koha 2.2 使用手冊

83
Koha 使使使使 採採採採採採採採採採採(GNU General Public License, GPL)採採採 (http://www.gnu.org/licenses/gpl.html ) ��. 採採 a. 採採採採 i. 採採 ii. 採採 iii. 採採採採 iv. 採採採採 v. 採採 vi. 採採 vii. 採採採採採採 viii. 採採 b. 採採採採採採 i. 採採 ii. 採採採 iii. 採採採採 iv. 採採採採 v. 採採採採 vi. 採採採 vii. Z39.50 採採採 viii. 採採採採 ix. 採採 x. 採採 c. 採採採採採採採採 d. 採採 e. 採採 ��. 採採採採採採 a. 採採採採採採採採採採 - 採 3.2. Authorised Values 3.3. Biblio Framework (MARC Structure) -- subfields 3.3.1. Authorised Value 3.3.2. Thesaurus 3.3.3. Plugins 3.3.4. Leader plugins 3.3.5. Link

Upload: maolins

Post on 02-Nov-2014

27 views

Category:

Documents


7 download

DESCRIPTION

 

TRANSCRIPT

Page 1: koha 2.2 使用手冊

Koha使用手冊

採用革努通用公共許可證(GNU General Public License GPL)第二版(httpwwwgnuorglicensesgplhtml)

設定a 系統偏好

i 管理ii 採訪

iii 權威記錄iv 館藏目錄v 流通

vi 讀者vii 線上公用目錄

viii 其他b 設定作業參數

i 分館ii 印表機

iii 館藏型式iv 讀者類別v 借閱規則

vi 停用字vii Z3950 伺服器

viii 採購預算ix 貨幣x 其他

c 設定書目資料參數d 工具e 樣版

線上公用目錄a 機讀編目格式書目架構 - 初體驗

32 Authorised Values 33 Biblio Framework (MARC Structure) -- subfields

331 Authorised Value 332 Thesaurus 333 Plugins 334 Leader plugins 335 Link

34 Koha to MARC Database Links 35 MARC Check 36 Thesaurus Structure 37 - User comments -

流通

採錄及編目

期刊

報表

定期維護

資料庫結構

翻譯

Koha 22 是整合式圖書館自動化系統(Integrated Library SystemILS)採用革努通用公共許可證(GNU General Public License GPL)授權的自由軟體Koha 給使用者四大自由

執行程式的自由不問原因 研究程式的自由並將程式修改符合自身的需求

再散布程式的自由以幫助親朋好友 改進程式的自由並把改進的結果回饋給社群使整個社群受益

它的功能包括編目線上目錄流通讀者期刊採購等模組

1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開 發此系統其功能符合 2000 年各層級圖書館資訊系統軟硬體規範書的要求適合臺灣地區

的圖書館使用2007 年 10 月已有七個單位採用此系統

Koha 目前已經發展到 Koha 229 發展版本為 Koha 30 計畫管理者為 Joshua FerraroLiblime 公司的技術總監

營運綜合性大型圖書館所需的功能Koha均已具備

線上公用目錄檢索全部館藏 讀者的資料庫 讀者借出及還入館藏 讀者推薦購買館藏 向代理商 出版社採錄館藏 購書經費管制 分館互借及個別管理 期刊訂閱 簽收管理

Koha 支援MARC 21 及 UNIMARC(CMARC) 書目格式

Koha 的最大優點是採用革努通用公共許可證即自由軟體不祗是軟體本身免費而且可以應圖書館要求自由修改程式交由廠商修改或自行修改圖書資訊學的基礎知識與實務

經驗加上 Apache HTTP ServerPerl 程式語言及MySQL 資料庫的應用能力就可以安裝 使用 Koha 雖然不需付費即可取得 Koha但仍需付費給協助安裝維護的廠商或圖書館自

行雇用的軟體人員不過整體費用仍低於使用專屬軟體

採用 Koha可以全面掌控圖書館的軟體及資料原始碼是開放的圖書館可自由地修改原 始碼以符合個別的需要專屬軟體的修改必須符合該軟體公司的政策

本文的對象是圖書館員不是電腦技術員未觸及安裝設定也不討論從其他系統匯入書目 資料及讀者資料的事宜有其他的文件討論該等事宜圖書館安裝 Koha並已從其他系統

將資料匯入後圖書館員才需要閱讀本文專注於調整參數及其他個別化的運作

第一章設定

下載及安裝之後Koha 還不能立即使用採用專屬軟體時廠商與圖書館經過頻繁的溝通後瞭解圖書館的屬性資料內容編目慣例等事宜後將軟體設定之後才交給圖書館驗收Koha 安裝之後圖書館需要花點時間來設定它這個程序沒什麼技術上的困難但頗

為費時有的圖書館把這個工作交給廠商執行等同於採用專屬軟體和程序祗是不必付 授權費並取得完整的內碼

安裝之後有兩個網址分別是讀者使用的線上公用目錄及圖書館員用的內部網路內部 網路係用於流通編目分類等事務內定值是一樣的內部網路多了「8080」本書以

財團法人佛教慈濟綜合醫院大林分院圖書館為例線上公用目錄網址是 httpdllibtzuchicomtw 圖書館員用的內部網路是 httpdllibtzuchicomtw

內部網路在MozillaFirefox 上做過全面的測試Internet Explorer祗能使用部份的功能線上公用目錄可在任何瀏覽器使用

圖 11 內部網路起始

以館員身份 mao 登入後出現內部網路的首頁

圖 12 內部網路

未登錄的讀者仍可使用線上公用目錄的部份功能

圖 13 線上公用目錄(OPAC) 起始

以讀者的借書證號碼登入後出現該讀者專屬的線上公用目錄

圖 14 線上公用目錄(OPAC)

現在就可以開始用 Koha 不過要忍耐需選擇參數(Parameters) 告訴 Koha 幾件重要的事它才會照著館員的意思去運作

在內部網路首頁的左下角系統管理裡有兩組待設定的參數 系統偏好系統參數安裝 時已設定部份參數其他的參數仍需要在此設定隨時可以修改已經設定的參數

圖 15 系統管理

別被這麼多參數嚇壞 我們將逐一詳細說明它們所需時間從幾小時至幾天依組織資料系 統的方式而定現在多花點時間將來就可以省事

從這個畫面依序介紹從「系統偏好」開始

11 系統偏好

這些參數應優先設定它控制 Koha 的主要工作

如果畫面不是中文繁體或簡體要求技術員重新安裝無法從任何的參數設定改變語系檔

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 2: koha 2.2 使用手冊

定期維護

資料庫結構

翻譯

Koha 22 是整合式圖書館自動化系統(Integrated Library SystemILS)採用革努通用公共許可證(GNU General Public License GPL)授權的自由軟體Koha 給使用者四大自由

執行程式的自由不問原因 研究程式的自由並將程式修改符合自身的需求

再散布程式的自由以幫助親朋好友 改進程式的自由並把改進的結果回饋給社群使整個社群受益

它的功能包括編目線上目錄流通讀者期刊採購等模組

1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開 發此系統其功能符合 2000 年各層級圖書館資訊系統軟硬體規範書的要求適合臺灣地區

的圖書館使用2007 年 10 月已有七個單位採用此系統

Koha 目前已經發展到 Koha 229 發展版本為 Koha 30 計畫管理者為 Joshua FerraroLiblime 公司的技術總監

營運綜合性大型圖書館所需的功能Koha均已具備

線上公用目錄檢索全部館藏 讀者的資料庫 讀者借出及還入館藏 讀者推薦購買館藏 向代理商 出版社採錄館藏 購書經費管制 分館互借及個別管理 期刊訂閱 簽收管理

Koha 支援MARC 21 及 UNIMARC(CMARC) 書目格式

Koha 的最大優點是採用革努通用公共許可證即自由軟體不祗是軟體本身免費而且可以應圖書館要求自由修改程式交由廠商修改或自行修改圖書資訊學的基礎知識與實務

經驗加上 Apache HTTP ServerPerl 程式語言及MySQL 資料庫的應用能力就可以安裝 使用 Koha 雖然不需付費即可取得 Koha但仍需付費給協助安裝維護的廠商或圖書館自

行雇用的軟體人員不過整體費用仍低於使用專屬軟體

採用 Koha可以全面掌控圖書館的軟體及資料原始碼是開放的圖書館可自由地修改原 始碼以符合個別的需要專屬軟體的修改必須符合該軟體公司的政策

本文的對象是圖書館員不是電腦技術員未觸及安裝設定也不討論從其他系統匯入書目 資料及讀者資料的事宜有其他的文件討論該等事宜圖書館安裝 Koha並已從其他系統

將資料匯入後圖書館員才需要閱讀本文專注於調整參數及其他個別化的運作

第一章設定

下載及安裝之後Koha 還不能立即使用採用專屬軟體時廠商與圖書館經過頻繁的溝通後瞭解圖書館的屬性資料內容編目慣例等事宜後將軟體設定之後才交給圖書館驗收Koha 安裝之後圖書館需要花點時間來設定它這個程序沒什麼技術上的困難但頗

為費時有的圖書館把這個工作交給廠商執行等同於採用專屬軟體和程序祗是不必付 授權費並取得完整的內碼

安裝之後有兩個網址分別是讀者使用的線上公用目錄及圖書館員用的內部網路內部 網路係用於流通編目分類等事務內定值是一樣的內部網路多了「8080」本書以

財團法人佛教慈濟綜合醫院大林分院圖書館為例線上公用目錄網址是 httpdllibtzuchicomtw 圖書館員用的內部網路是 httpdllibtzuchicomtw

內部網路在MozillaFirefox 上做過全面的測試Internet Explorer祗能使用部份的功能線上公用目錄可在任何瀏覽器使用

圖 11 內部網路起始

以館員身份 mao 登入後出現內部網路的首頁

圖 12 內部網路

未登錄的讀者仍可使用線上公用目錄的部份功能

圖 13 線上公用目錄(OPAC) 起始

以讀者的借書證號碼登入後出現該讀者專屬的線上公用目錄

圖 14 線上公用目錄(OPAC)

現在就可以開始用 Koha 不過要忍耐需選擇參數(Parameters) 告訴 Koha 幾件重要的事它才會照著館員的意思去運作

在內部網路首頁的左下角系統管理裡有兩組待設定的參數 系統偏好系統參數安裝 時已設定部份參數其他的參數仍需要在此設定隨時可以修改已經設定的參數

圖 15 系統管理

別被這麼多參數嚇壞 我們將逐一詳細說明它們所需時間從幾小時至幾天依組織資料系 統的方式而定現在多花點時間將來就可以省事

從這個畫面依序介紹從「系統偏好」開始

11 系統偏好

這些參數應優先設定它控制 Koha 的主要工作

如果畫面不是中文繁體或簡體要求技術員重新安裝無法從任何的參數設定改變語系檔

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 3: koha 2.2 使用手冊

Koha 支援MARC 21 及 UNIMARC(CMARC) 書目格式

Koha 的最大優點是採用革努通用公共許可證即自由軟體不祗是軟體本身免費而且可以應圖書館要求自由修改程式交由廠商修改或自行修改圖書資訊學的基礎知識與實務

經驗加上 Apache HTTP ServerPerl 程式語言及MySQL 資料庫的應用能力就可以安裝 使用 Koha 雖然不需付費即可取得 Koha但仍需付費給協助安裝維護的廠商或圖書館自

行雇用的軟體人員不過整體費用仍低於使用專屬軟體

採用 Koha可以全面掌控圖書館的軟體及資料原始碼是開放的圖書館可自由地修改原 始碼以符合個別的需要專屬軟體的修改必須符合該軟體公司的政策

本文的對象是圖書館員不是電腦技術員未觸及安裝設定也不討論從其他系統匯入書目 資料及讀者資料的事宜有其他的文件討論該等事宜圖書館安裝 Koha並已從其他系統

將資料匯入後圖書館員才需要閱讀本文專注於調整參數及其他個別化的運作

第一章設定

下載及安裝之後Koha 還不能立即使用採用專屬軟體時廠商與圖書館經過頻繁的溝通後瞭解圖書館的屬性資料內容編目慣例等事宜後將軟體設定之後才交給圖書館驗收Koha 安裝之後圖書館需要花點時間來設定它這個程序沒什麼技術上的困難但頗

為費時有的圖書館把這個工作交給廠商執行等同於採用專屬軟體和程序祗是不必付 授權費並取得完整的內碼

安裝之後有兩個網址分別是讀者使用的線上公用目錄及圖書館員用的內部網路內部 網路係用於流通編目分類等事務內定值是一樣的內部網路多了「8080」本書以

財團法人佛教慈濟綜合醫院大林分院圖書館為例線上公用目錄網址是 httpdllibtzuchicomtw 圖書館員用的內部網路是 httpdllibtzuchicomtw

內部網路在MozillaFirefox 上做過全面的測試Internet Explorer祗能使用部份的功能線上公用目錄可在任何瀏覽器使用

圖 11 內部網路起始

以館員身份 mao 登入後出現內部網路的首頁

圖 12 內部網路

未登錄的讀者仍可使用線上公用目錄的部份功能

圖 13 線上公用目錄(OPAC) 起始

以讀者的借書證號碼登入後出現該讀者專屬的線上公用目錄

圖 14 線上公用目錄(OPAC)

現在就可以開始用 Koha 不過要忍耐需選擇參數(Parameters) 告訴 Koha 幾件重要的事它才會照著館員的意思去運作

在內部網路首頁的左下角系統管理裡有兩組待設定的參數 系統偏好系統參數安裝 時已設定部份參數其他的參數仍需要在此設定隨時可以修改已經設定的參數

圖 15 系統管理

別被這麼多參數嚇壞 我們將逐一詳細說明它們所需時間從幾小時至幾天依組織資料系 統的方式而定現在多花點時間將來就可以省事

從這個畫面依序介紹從「系統偏好」開始

11 系統偏好

這些參數應優先設定它控制 Koha 的主要工作

如果畫面不是中文繁體或簡體要求技術員重新安裝無法從任何的參數設定改變語系檔

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 4: koha 2.2 使用手冊

內部網路在MozillaFirefox 上做過全面的測試Internet Explorer祗能使用部份的功能線上公用目錄可在任何瀏覽器使用

圖 11 內部網路起始

以館員身份 mao 登入後出現內部網路的首頁

圖 12 內部網路

未登錄的讀者仍可使用線上公用目錄的部份功能

圖 13 線上公用目錄(OPAC) 起始

以讀者的借書證號碼登入後出現該讀者專屬的線上公用目錄

圖 14 線上公用目錄(OPAC)

現在就可以開始用 Koha 不過要忍耐需選擇參數(Parameters) 告訴 Koha 幾件重要的事它才會照著館員的意思去運作

在內部網路首頁的左下角系統管理裡有兩組待設定的參數 系統偏好系統參數安裝 時已設定部份參數其他的參數仍需要在此設定隨時可以修改已經設定的參數

圖 15 系統管理

別被這麼多參數嚇壞 我們將逐一詳細說明它們所需時間從幾小時至幾天依組織資料系 統的方式而定現在多花點時間將來就可以省事

從這個畫面依序介紹從「系統偏好」開始

11 系統偏好

這些參數應優先設定它控制 Koha 的主要工作

如果畫面不是中文繁體或簡體要求技術員重新安裝無法從任何的參數設定改變語系檔

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 5: koha 2.2 使用手冊

圖 12 內部網路

未登錄的讀者仍可使用線上公用目錄的部份功能

圖 13 線上公用目錄(OPAC) 起始

以讀者的借書證號碼登入後出現該讀者專屬的線上公用目錄

圖 14 線上公用目錄(OPAC)

現在就可以開始用 Koha 不過要忍耐需選擇參數(Parameters) 告訴 Koha 幾件重要的事它才會照著館員的意思去運作

在內部網路首頁的左下角系統管理裡有兩組待設定的參數 系統偏好系統參數安裝 時已設定部份參數其他的參數仍需要在此設定隨時可以修改已經設定的參數

圖 15 系統管理

別被這麼多參數嚇壞 我們將逐一詳細說明它們所需時間從幾小時至幾天依組織資料系 統的方式而定現在多花點時間將來就可以省事

從這個畫面依序介紹從「系統偏好」開始

11 系統偏好

這些參數應優先設定它控制 Koha 的主要工作

如果畫面不是中文繁體或簡體要求技術員重新安裝無法從任何的參數設定改變語系檔

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 6: koha 2.2 使用手冊

圖 13 線上公用目錄(OPAC) 起始

以讀者的借書證號碼登入後出現該讀者專屬的線上公用目錄

圖 14 線上公用目錄(OPAC)

現在就可以開始用 Koha 不過要忍耐需選擇參數(Parameters) 告訴 Koha 幾件重要的事它才會照著館員的意思去運作

在內部網路首頁的左下角系統管理裡有兩組待設定的參數 系統偏好系統參數安裝 時已設定部份參數其他的參數仍需要在此設定隨時可以修改已經設定的參數

圖 15 系統管理

別被這麼多參數嚇壞 我們將逐一詳細說明它們所需時間從幾小時至幾天依組織資料系 統的方式而定現在多花點時間將來就可以省事

從這個畫面依序介紹從「系統偏好」開始

11 系統偏好

這些參數應優先設定它控制 Koha 的主要工作

如果畫面不是中文繁體或簡體要求技術員重新安裝無法從任何的參數設定改變語系檔

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 7: koha 2.2 使用手冊

圖 15 系統管理

別被這麼多參數嚇壞 我們將逐一詳細說明它們所需時間從幾小時至幾天依組織資料系 統的方式而定現在多花點時間將來就可以省事

從這個畫面依序介紹從「系統偏好」開始

11 系統偏好

這些參數應優先設定它控制 Koha 的主要工作

如果畫面不是中文繁體或簡體要求技術員重新安裝無法從任何的參數設定改變語系檔

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 8: koha 2.2 使用手冊

圖 16 系統偏好 - 其他

系統偏好很簡單 祗有三個欄位 變數數值說明依其性質分為幾類管理採訪權威記錄館藏目錄流通內部網路讀者線上公用目錄其他有些偏好不需要改變它

內定值就可以了

點選「編輯」就可以改變偏好不要點選「刪除」那是系統管理者的特權即使要刪除它也需先備份最下緣有「新增系統偏好」絕大部份的圖書館不需要刪除也不需要新增系統

偏好祗有修改 Koha 程式後才可能刪除或新增系統偏好

Koha 是自由軟體把所有的選擇權都交給使用者所以還是保留刪除或新增系統偏好的權 利給使用者

偏好設定後儲存在 Koha 資料庫的系統偏好(systempreferences) 表裡

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 9: koha 2.2 使用手冊

編輯偏好時進入標準化的畫面有固定的選項以採訪為例

圖 17 修改系統偏好 - 採訪

點選第一行變數 Acquisitions 右方的編輯呈現如下的畫面

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 10: koha 2.2 使用手冊

圖 18 修改系統偏好 - 採訪 -gt Acquisitions

上半段的對話盒簡短描述系統偏好的內容 偏好名稱及其數值修改數值後即可儲存改變在下的對話盒標示為「Koha 內部」並且提醒「注意你毋須對以下的預設值作出任何修改」變數型式及變數選項兩個內容在本例裡它的變數型式是選擇(choice) 祗能

從選單裡擇一而用它的值存在變數選項裡

其他的變數型式 YesNoIntegerTextareaFloatThemesLanguages 留待適當的時機再說明Koha 把幾乎用不到的改變的都提供出來藉著自由軟體的特性增強使用者的信心

設定偏好沒有順序以下就逐一設定它們

111 管理

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 11: koha 2.2 使用手冊

有兩個偏好可設定

dateformat[日期格式]

insecure[安全警戒]

日期格式

有美制(us)公制(metric)或國際標準制(iso)可選

美制(us) = mmddyyyy 公制(metric) = ddmmyyyy 國際標準制(iso) = yyyymmdd

此偏好控制日期的顯示方式但資料庫裡的日期格式不能從這裡設定臺灣習慣的是國際標準制(iso) = yyyymmdd

安全警戒

祗有一個館員的圖書館每次開機都需要簽入有點纍贅可以將此偏好設為「yes」把安全警戒關掉所有資料都開放給每個上網的人不過這種做法很冒險最好還是設為「no」 打開安全警戒

112 採訪

有兩個偏好

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 12: koha 2.2 使用手冊

acquisitions[採訪模式]

gist[營業稅]

採訪模式

有兩種 標準(normal)或簡單(simple)標準模式下新增資料入館藏時系統會追蹤訂單更新預算及廠商資料簡單模式下單純新增資料入館藏不做任何更新所以要管控預算及廠商就選擇標準(normal)若另有其他的預算及稽核工具則選擇簡單(simple)

營業稅

如果會計單位要求將營業稅另外計算則把營業稅登入臺灣地區的營業稅率是百分之五 005

向讀者收取的影印費逾期罰款等不計入一定要算則在Item types 及 Issuing rules 的偏好中直接加總

113 權威記錄

有兩個偏好

a AuthDisplayHierarchy[顯示權威記錄的階層] b authoritysep[分隔符號]

顯示權威記錄的階層

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 13: koha 2.2 使用手冊

內定值為 1 顯示權威記錄的階層

分隔符號

用於權威記錄內的分隔符號內定值為兩個連接號「-- 」

Koha 需要知道分隔主題標目的符號臺灣追隨美國的慣例以兩個連接號分隔不同階層的主題標目如 「政治 -- 臺灣」如果採用其他的分隔符號應該告訴 Koha

Koha 處理權威記錄的細節於設定機讀編目格式的偏好裡

114 館藏目錄

館藏目錄的偏好設定較多共有 15個

ISBD [國際書目著錄標準]

IntranetBiblioDefaultView

LabelMARCView

MARCOrgCode

ReceiveBackIssues

advancedMARCedito

autoBarcode [自動給定條碼號]

hide_marc [隱藏特定的MARC欄位或分欄]

itemcallnumber [索書號]

marc [使用機讀編目格式]

marcflavour [機讀編目格式種類]

serialsadditems

sortbynonfiling

z3950AuthorAuthFields

z3950NormalizeAuthor

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 14: koha 2.2 使用手冊

國際書目著錄標準

國際圖書館協會聯盟(International Federation of Library Associations and Institutions IFLA)訂定的書目著錄準則把細目順序及標點符號規定的清清楚楚2007年出版的統整版取代了過去的七種標準(圖書地圖連續性出版品錄音資料電腦檔等)

International standard bibliographic description (ISBD) recommended by the ISBD Review Group approved by the Standing Committee of the IFLA Cataloguing Section mdash Preliminary consolidated ed mdash Muumlnchen KG Saur 2007 mdash 1 vol (loose-leaf) 32 cm mdash (IFLA series on bibliographic control vol 31) mdash ISBN 978-3-598-24280-9

在這個偏好裡以指令或算式設定變數的內容指示 Koha 顯示國際書目著錄標準格式的書目資料線上說明的例子以UNIMARCCMARC 為例

MARC 21 已經內含英美編目規則第二版及標點符號祗要給欄位就夠了

050|ltlabelgt索書號 ltlabelgt|082a050a 050b|ltbrgtltbrgt 100|ltlabelgt主要款目 ltlabelgt|100a 100b 100c 100d110a 110b130a|ltbrgt 245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260|| 250a 250b-- 260a 260b 260c| 300|ltbrgtltlabelgt ltlabelgt|300a 300b 300c|ltbrgt 020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt 440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt 500||n500a|ltbrgt 511||511a | 520|ltlabelgt ltlabelgt|n520a 520b| 600|ltbrgtltlabelgt主題標目 ltlabelgt| 600a| 650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y| 651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y| 852|ltbrgtltbrgtltlabelgt館藏地 ltlabelgt|n852a 852b 852c|

MARC 21 比較麻煩參照 9 使用者回應

自動給定條碼號

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 15: koha 2.2 使用手冊

設定為「是」(yes)Koha 就能自動給定條碼號不必指定起始號碼或條碼類型若已另行印製條碼則設定為「否」(no) 在鍵入價格編目日期時一併將條碼鍵入書目記錄裡

隱藏特定的MARC 資料

使用MARC記錄的圖書館但不想看到太多的MARC欄位免得圖書館員被複雜的標籤及 分欄搞昏頭

索書號

設定其他的MARC偏好後再設定此偏好將MARC的標籤及分欄抓出來製作成索書號 別忘了做個小抄設定其他偏好時拿出來參考免得衝突

設定索書號欄位後每個複本都有獨立的索書號MARC的標籤祗有個別複本的索書號必須在這裡設定才能有整體的索書號第一複本在甲館為不外借的參考書第二複本在乙館屬於外借館藏必須設定索書號Koha 才能把所有的複本整合在一起

借閱規則係依照圖書的館藏地而定不是依照索書號而定複本需要不同的借閱規則時應 分別製作書目記錄每個館藏地一個書目記錄

匯入外部MARC書目記錄無法一併匯入索書號時可以請程式設計師寫個小程式編製 索書號並把它放回原來的館藏書籤裡

使用機讀編目格式

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 16: koha 2.2 使用手冊

以這個偏好設定使用或不使用機讀編目格式

機讀編目格式種類

Koha 不僅可以設定使用或不使用機讀編目格式還可以選擇使用MARC 21 或UNIMARCCMARCKoha 即依照偏好的設定解讀書目資料

115 流通

有六種偏好

a ReturnBeforeExpiry[圖書到期日在借書證有效日之前] b maxoutstanding[最高應付費用] c maxreserves[預約額度] d noissuescharge[拒絕借書的應付費用] e patronimages[讀者照片] f printcirculationslips[ 列印借書清單 ]

圖書到期日在借書證有效日之前

設定為是則不允許圖書的到期日超過借書證有效日Koha 重新調整到期日為有效日的最 後一天

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 17: koha 2.2 使用手冊

學校圖書館很喜歡這個偏好學生的圖書到期日等同於借書證的有效日期老師的圖書到期 日等同於聘書的有效日期

最高應付費用

讀者積欠圖書館費用達到這個額度時不再幫該讀者辦理各項預約事宜祗提供基本的服務此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為0

預約額度

設定每個讀者同時可以預約的最高數量

禁止借書的應付費用

讀者積欠圖書館費用達到這個額度時禁止該讀者繼續借書此數值是整數金額沒有小數不管讀者積欠多少錢仍提供同樣服務則設定為 0

讀者照片

在內部網路顯示讀者照片 1 顯示0 隱藏

列印借書清單

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 18: koha 2.2 使用手冊

以印表機印出正式的借書清單則設定偏好為 1不印則設定為 0

116 讀者

有三種偏好

a NotifyBorrowerDeparture[提醒借書證到期] b autoMemberNum[自動給定讀者號] c checkdigit[檢查碼]

提醒借書證到期

設定值為天數讀者借書時先查核借書證的有效日有效日少於指定的天數時發出提示訊息借書證有效日為 6月 30 日設定提醒借書證有效日到期為 7則從 6月 23日開始借書時會提示該讀者的有效日學生的借書權利在畢業離校後就失效圖書館藉此提示讀者流通偏好設定的「圖書到期日在借書證有效日之前」設定到期日此偏好祗提示不

限制

自動給定讀者號

新申請閱覽證時祗要在這個偏好號設定為 1Koha 就自動給定讀者號預先已印好閱覽證的讀者號時則需設定為 0人工輸入讀者號編目偏好裡的「自動給定條碼號」設定其

功能類似對象為圖書的條碼號

「自動給定讀者號」與「自動給定條碼號」都是用於可見的外部號碼Koha 還可以另外給定內部控制用的讀者號與圖書條碼號用於內部資料庫的各表格之間這些內部控制用的號

碼通常自動給定不勞圖書館員操心

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 19: koha 2.2 使用手冊

檢查碼

檢查讀者號的有效性通常應選擇 none1999 年紐西蘭的Katipo公司替赫羅范努瓦圖書館信託(Horowhenua Library TrustHLT)開發此系統後赫羅范努瓦圖書館信託把這個功能捐出來若採用與赫羅范努瓦圖書館信託相同的讀者號系統就可以選擇Katipo

117 線上公用目錄

有 26種偏好

a AmazonAssocTag b AmazonContent c AmazonDevKey d AnonSuggestions e BiblioDefaultView[顯示書目格式] f Disable_Dictionary[字典查詢] g LibraryName[圖書館名稱] h OpacNav i OpacPasswordChange[密碼變更] j SubscriptionHistory[期刊資訊] k hidelostitems[隱藏遺失的館藏] l opacbookbag m opaccolorstylesheet n opaccredits o opacheader p opaclanguages[語言] q opaclanguagesdisplay r opaclargeimage[自訂大圖示] s opaclayoutstylesheet t opacreadinghistory u opacsmallimage[自訂小圖示] v opacstylesheet[串接樣式表] w opacthemes[主題] x opacuserlogin y suggestion[採訪建議] z virtualshelves [虛擬書架]

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 20: koha 2.2 使用手冊

顯示書目格式

檢索目錄後顯示在螢幕的格式有三個選擇 條列式(normal)機讀編目格式(marc)國際書目著錄標準(isbd)

條列式顯示基本的書目資訊Koha 的內定格式 機讀編目格式顯示書目資料完整的機讀編目格式

國際書目著錄標準顯示國際圖書館協會聯盟公布的書目格式

可修改 HTML 樣版修改顯示的格式已顯示的格式也可以即時切換初始值為條 列式

字典查詢

Koha 的線上公用目錄允許讀者預查目錄的書名作者標題以減少不正確的回應 不過有些圖書館寧願關閉此功能

進入進階查詢後點選書名作者標題輸入欄右邊的三個黑點就可使用此功能

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 21: koha 2.2 使用手冊

圖 19 字典查詢

選擇傳回來的字詞再到館藏查詢有助於得到更精準的結果

圖書館名稱

顯示在線上公用目錄的圖書館名稱也可以是其他的訊息

可使用 HTML 語法 內定的訊息是

ltigtltbgtKohaltbrgtFree Software ILSltbrgtltbrgtltbgtKoha a gift a contributionltbrgt in Maoriltigt

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 22: koha 2.2 使用手冊

在大小括號內的是 HTML 標籤 在 ltigt 與 ltigt 之間的文字是斜體字 在 ltbgt 與 ltbgt 之間的文字是黑體字 ltbrgt 表示此列結束

密碼變更

讀者經線上公用目錄變更密碼特別適合使用輕量型目錄存取通訊協定(LDAP)認證的環境 因為 Koha 無權控制輕量通訊協定的密碼

期刊資訊

設定讀者看到的期刊訂閱資訊有兩個選項 精簡(simplified)或完整(full) 內定值是精簡

精簡

讀者可以看到 期刊名稱到館的日期刊期最新訂閱日期(不再續訂時則顯示最後收到的刊期) 然後是所有已到及未到的期刊

完整

讀者可以看到 期刊名稱以及各期的的狀況 到館將到遲到遺失等

隱藏遺失的館藏

不想讓讀者看到遺失的館藏則設定為「是」反之則設為「否」

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 23: koha 2.2 使用手冊

語言

此偏好設定控制所有的Koha顯示螢幕包括線上公用目錄目前可用的語言有英文(en)及法文(fr) 繁體中文(zh-TW)已翻譯完成另外還有義大利文等選擇「是」則

取用名單內最前的語言

自訂大圖示

以自訂的圖片取代 Koha 內訂的圖片大標誌的內定值是 310x440 圖素

自訂小圖示

如同自訂大標誌此偏好設定可使用自訂的小標誌顯示在線上公用目錄各頁的左上 角大小為 35x50 圖素

串接樣式表

Koha 的畫面與全球資訊網聯盟推的標準相容使用串接樣式表呈現其畫面內定檔案 為 opaccss 置於 usrlocalkohaopachtdocsopac-tmpldefaultenincludes 目錄內可以

在系統偏好內設定第二個選擇 opac-tmplcssopac2css

鍵入完整的 href 路徑就可以改變線上公用目錄的串接樣式表如opac-tmpldefaultenincludesopaccss

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 24: koha 2.2 使用手冊

主題

Koha 以 HTML 的樣版建立網頁顯示在螢幕上修改樣版就可改變螢幕的樣子

Koha 有多個樣版串接樣式表(css)和納爾遜維(npl) 較為特別針對線上公用目錄而設 計

串接樣式表

Koha 的內定樣版是串接樣式表由法國人 Paul Poulain 用串接樣式表設計所以簡稱為css

納爾遜維

也使用串接樣式表由 Owen Leonard 為美國俄亥俄州的納爾遜維公共圖書館(Nelsonville Public Library) 設計出來簡稱為 npl

如同語言(opaclanguages)偏好Koha 先用選定的主題若找不到就用內定的主題

主題的模版多半可在 usrlocalkohaopachtdocsopac-tmpl 目錄下找到

採訪建議

若設為 1 讀者可從線上公用目錄推薦購買讀者推薦書籍後該書的狀況為已提出(ASKED)圖書館員依權責設定其狀況為拒絕(REJECTED)或採訪中(ORDERED)到館之後其狀況則為在館內(AVAILABLE)還沒有進入在館內狀況前每個讀者都

可從線上公用目錄看到其狀況

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 25: koha 2.2 使用手冊

尚未啟用採訪建議參數時則不會出現輸入採訪建議的按鈕

虛擬書架

偏好設定為是讀者可設定及管理自己的虛擬書架有三種書架 私人書架公開書架 自由書架

私人書架

祗能被建立的讀者自己看到及使用從館藏看到將來想要讀的書可列入此書架

公開書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架不過祗有 建立者本人才能修改它可當成老師的指定參考書目圖書館把暢銷書列入

自由書架

登入線上公用目錄的讀者都可以看到別人或自己建立的公開書架並修改它 某個讀者可建立「最佳古典文學書目」其他讀者再增刪修改它的內容

118 其他

有 6個偏好

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 26: koha 2.2 使用手冊

a delimiter[分隔符號] b IndependantBranches[分館獨立] c KohaAdminEmailAddress[管理者電子郵件] d MIME[多用途網際網路郵件延伸標準] e MinPasswordLength[密碼長度] f timeout[自動登出]

分隔符號

輸出報表等統計資料時Koha 可產生有分隔符號的檔案以備其他應用程式讀取此 偏好即是設定分隔符號如設定逗點為分隔符號可產生 comma-separated value

(csv) 檔案供試算表等軟體使用

分館獨立

設定為是分館被視為獨立的圖書館共用一個資料庫經過授權的圖書館員可以新增基本的書目資料或借出還回資料庫裡的任何一本書但分館的圖書館員不可以為其他分館新增修改書目或讀者資料超級圖書館員仍有特權可新增修改書目或讀者資料不受此偏

好的限制

此偏好不影響線上公用目錄的畫面搜尋結果仍顯示所有分館的館藏

管理者電郵地址

讀者要求更改相關記錄時寄到此電郵地址

讀者登入線上公用目錄檢發現個人資料有誤時Koha 提供一個表格讓讀者填寫然後寄 給管理者電郵地址檢視後採取適當步驟此偏好即設定此電郵地址

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 27: koha 2.2 使用手冊

多用途網際網路郵件延伸標準

Koha 可以輸出 OpenOfficeorg 或其他格式的統計報表以此設定選擇輸出的格式

密碼長度

讀者的密碼長度不得小於設定值

自動登出

停滯的時間長度以秒計超過這個時間必須重新登入

把系統偏好設定後回到系統參數頁再使用其他的功能

119 使用者意見

(中文地區的Koha 使用者可以把意見寄到這裡 mao AT linsfjuedu DOT tw)

Joshua Allen Holm 的意見

在國際書目著錄標準裡有點問題索書號的 082 呼叫 050 時不會顯示

改成這個樣子就能解決此問題

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 28: koha 2.2 使用手冊

082|ltlabelgtCall Number ltlabelgt|082a|ltbrgtltbrgt

050|ltlabelgtCall Number ltlabellt|050a 050b|ltbrgtltbrgt100|ltlabelgtMain Entry ltlabelgt|100a 100b 100c100d110a110b130a|ltbrgt245|ltlabelgt ltlabelgt|245a 245b 245c 245h 246i 246a| 260||250a 250b-- 260a 260b 260c|300|ltbrgtltlabelgt ltlabelgt|300a 300b300c|ltbrgt020|ltbrgtltlabelgt ISBNltlabelgt| 020a 024a|ltbrgt440|ltbrgtltlabelgt ltlabelgt|440a 440v|ltbrgt500||n500a|ltbrgt511||511a |520|ltlabelgt ltlabelgt|n520a 520b|600|ltbrgtltlabelgtSubjects ltlabelgt| 600a|650|ltlabelgt ltlabelgt|n650a -- 650x-- 650z-- 650y|651|ltlabelgt ltlabelgt|n651a -- 651x-- 651z-- 651y|852|ltbrgtltbrgtltlabelgtHeld at ltlabelgt|n852a 852b 852c|

有一點需注意剪貼上述內容時先移除所有的直線或改變 ISBD的變數為 Textarea

Thomas Dukleth 的意見

ISBD對應至MARC 21的內容不正確可修改為

100|| 100a 100b 100c 100d 110a 110b 110c 110d 110e 110f 110g 130a 130d 130f 130g 130h 130k 130l 130m 130n 130o 130p 130r 130s 130t |ltbrgtltbrgt 245|| 245a 245b 245f 245g 245k 245n 245p 245s 245h | 246|| 246i 246a 246b 246f 246g 246n 246p 246h | 242|| = 242a 242b 242n 242p 242h | 245|| 245c | 242|| = 242c | 250| - | 250a 250b | 254| | 254a | 255| | 255a 255b 255c 255d 255e 255f 255g | 256| | 256a | 257| | 257a | 258| | 258a 258b |

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 29: koha 2.2 使用手冊

260| - | 260a 260b 260c | 300| - | 300a 300b 300c 300d 300e 300f 300g | 306| - | 306a | 307| - | 307a 307b | 310| - | 310a 310b | 321| - | 321a 321b | 340| - | 3403 340a 340b 340c 340d 340e 340f 340h 340i | 342| - | 342a 342b 342c 342d 342e 342f 342g 342h 342i 342j 342k 342l 342m 342n 342o 342p 342q 342r 342s 342t 342u 342v 342w | 343| - | 343a 343b 343c 343d 343e 343f 343g 343h 343i | 351| - | 3513 351a 351b 351c | 352| - | 352a 352b 352c 352d 352e 352f 352g 352i 352q | 362| - | 362a 351z | 440| - | 440a 440n 440p 440v 440x | 490| - | 490a 490v 490x | 800| - | 800a 800b 800c 800d 800e 800f 800g 800h 800j 800k 800l 800m 800n 800o 800p 800q 800r 800s 800t 800u 800v | 810| - | 810a 810b 810c 810d 810e 810f 810g 810h 810k 810l 810m 810n 810o 810p 810r 810s 810t 810u 810v | 811| - | 811a 811c 811d 811e 811f 811g 811h 811k 811l 811n 811p 811q 811s 811t 811u 811v | 830| - | 830a 830d 830f 830g 830h 830k 830l 830m 830n 830o 830p 830r 830s 830t 830v | 500|ltbrgtltbrgt| 5003 500a | 501|ltbrgtltbrgt| 501a | 502|ltbrgtltbrgt| 502a | 504|ltbrgtltbrgt| 504a | 505|ltbrgtltbrgt| 505a 505t 505r 505g 505u | 506|ltbrgtltbrgt| 5063 506a 506b 506c 506d 506u | 507|ltbrgtltbrgt| 507a 507b | 508|ltbrgtltbrgt| 508a 508a | 510|ltbrgtltbrgt| 5103 510a 510x 510c 510b | 511|ltbrgtltbrgt| 511a | 513|ltbrgtltbrgt| 513a 513b | 514|ltbrgtltbrgt| 514z 514a 514b 514c 514d 514e 514f 514g 514h 514i 514j 514k 514m 514u | 515|ltbrgtltbrgt| 515a | 516|ltbrgtltbrgt| 516a | 518|ltbrgtltbrgt| 5183 518a | 520|ltbrgtltbrgt| 5203 520a 520b 520u | 521|ltbrgtltbrgt| 5213 521a 521b | 522|ltbrgtltbrgt| 522a | 524|ltbrgtltbrgt| 524a | 525|ltbrgtltbrgt| 525a | 526|ltbrgtltbrgt|n510i n510a 510b 510c 510d n510x | 530|ltbrgtltbrgt|n5063 n506a 506b 506c 506d n506u | 533|ltbrgtltbrgt|n5333 n533a n533b n533c n533d n533e n533f n533m n533n | 534|ltbrgtltbrgt|n533p n533a n533b n533c n533d n533e n533f n533m n533n n533t n533x n533z | 535|ltbrgtltbrgt|n5353 n535a n535b n535c n535d |

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 30: koha 2.2 使用手冊

538|ltbrgtltbrgt|n5383 n538a n538i n538u | 540|ltbrgtltbrgt|n5403 n540a 540b 540c 540d n520u | 544|ltbrgtltbrgt|n5443 n544a n544b n544c n544d n544e n544n | 545|ltbrgtltbrgt|n545a 545b n545u | 546|ltbrgtltbrgt|n5463 n546a 546b | 547|ltbrgtltbrgt|n547a | 550|ltbrgtltbrgt| 550a | 552|ltbrgtltbrgt| 552z 552a 552b 552c 552d 552e 552f 552g 552h 552i 552j 552k 552l 552m 552n 562o 552p 552u | 555|ltbrgtltbrgt| 5553 555a 555b 555c 555d 555u | 556|ltbrgtltbrgt| 556a 506z | 563|ltbrgtltbrgt| 5633 563a 563u | 565|ltbrgtltbrgt| 5653 565a 565b 565c 565d 565e | 567|ltbrgtltbrgt| 567a | 580|ltbrgtltbrgt| 580a | 581|ltbrgtltbrgt| 5633 581a 581z | 584|ltbrgtltbrgt| 5843 584a 584b | 585|ltbrgtltbrgt| 5853 585a | 586|ltbrgtltbrgt| 5863 586a | 020|ltbrgtltbrgtltlabelgtISBN ltlabelgt| 020a 020c | 022|ltbrgtltbrgtltlabelgtISSN ltlabelgt| 022a | 222| = | 222a 222b | 210| = | 210a 210b | 024|ltbrgtltbrgtltlabelgtStandard No ltlabelgt| 024a 024c 024d 0242 | 027|ltbrgtltbrgtltlabelgtStandard Tech Report No ltlabelgt| 027a | 028|ltbrgtltbrgtltlabelgtPublisher No ltlabelgt| 028a 028b | 013|ltbrgtltbrgtltlabelgtPatent No ltlabelgt| 013a 013b 013c 013d 013e 013f | 030|ltbrgtltbrgtltlabelgtCODEN ltlabelgt| 030a | 037|ltbrgtltbrgtltlabelgtSource ltlabelgt| 037a 037b 037c 037f 037g 037n | 010|ltbrgtltbrgtltlabelgtLCCN ltlabelgt| 010a | 015|ltbrgtltbrgtltlabelgtNat Bib No ltlabelgt| 015a 0152 | 016|ltbrgtltbrgtltlabelgtNat Bib Agency Control No ltlabelgt| 016a 0162 | 600|ltbrgtltbrgtltlabelgtSubjects--Personal Names ltlabelgt|n6003 n600a 600b 600c 600d 600e 600f 600g 600h --600k 600l 600m 600n 600o --600p 600r 600s 600t 600u --600x--600z--600y--600v| 610|ltbrgtltbrgtltlabelgtSubjects--Corporate Names ltlabelgt|n6103 n610a 610b 610c 610d 610e 610f 610g 610h --610k 610l 610m 610n 610o --610p 610r 610s 610t 610u --610x--610z--610y--610v| 611|ltbrgtltbrgtltlabelgtSubjects--Meeting Names ltlabelgt|n6113 n611a 611b 611c 611d 611e 611f 611g 611h --611k 611l 611m 611n 611o --611p 611r 611s 611t 611u --611x--611z--611y--611v| 630|ltbrgtltbrgtltlabelgtSubjects--Uniform Titles ltlabelgt|n630a 630b 630c 630d 630e 630f 630g 630h --630k 630l 630m 630n 630o --630p 630r 630s 630t --630x--630z--630y--630v| 648|ltbrgtltbrgtltlabelgtSubjects--Chronological Terms ltlabelgt|n6483 n648a --648x--648z--648y--648v| 650|ltbrgtltbrgtltlabelgtSubjects--Topical Terms ltlabelgt|n6503 n650a 650b 650c 650d 650e --650x--650z--650y--650v| 651|ltbrgtltbrgtltlabelgtSubjects--Geographic Terms ltlabelgt|n6513 n651a 651b 651c 651d 651e --651x--651z--651y--651v| 653|ltbrgtltbrgtltlabelgtSubjects--Index Terms ltlabelgt| 653a | 654|ltbrgtltbrgtltlabelgtSubjects--Facted Index Terms ltlabelgt|n6543 n654a--654b--

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 31: koha 2.2 使用手冊

654x--654z--654y--654v| 655|ltbrgtltbrgtltlabelgtIndex Terms--GenreForm ltlabelgt|n6553 n655a--655b--655x --655z--655y--655v| 656|ltbrgtltbrgtltlabelgtIndex Terms--Occupation ltlabelgt|n6563 n656a--656k--656x--656z--656y--656v| 657|ltbrgtltbrgtltlabelgtIndex Terms--Function ltlabelgt|n6573 n657a--657x--657z--657y--657v| 658|ltbrgtltbrgtltlabelgtIndex Terms--Curriculum Objective ltlabelgt|n658a--658b--658c--658d--658v| 050|ltbrgtltbrgtltlabelgtLC Class No ltlabelgt| 050a 050b | 082|ltbrgtltbrgtltlabelgtDewey Class No ltlabelgt| 082a 082b | 080|ltbrgtltbrgtltlabelgtUniversal Decimal Class No ltlabelgt| 080a 080x 080b | 070|ltbrgtltbrgtltlabelgtNational Agricultural Library Call No ltlabelgt| 070a 070b | 060|ltbrgtltbrgtltlabelgtNational Library of Medicine Call No ltlabelgt| 060a 060b | 074|ltbrgtltbrgtltlabelgtGPO Item No ltlabelgt| 074a | 086|ltbrgtltbrgtltlabelgtGov Doc Class No ltlabelgt| 086a | 088|ltbrgtltbrgtltlabelgtReport No ltlabelgt| 088a |

Paul Poulain 的意見

解說索書號

弄清楚兩件事情才能定義索書號

分類號 =gt 圖書之間的關係很多圖書館用杜威分類法中國圖書分類法或美國國會分類法

索書號 =gt 圖書在書架上的位置

很多圖書館把分類號當成索書號用但仍有些出入 一本書有一個索書號但可能有多個分類號

多本書的分類號相同可能共用同一個索書號或不同的索書號

分類號是書目層索書號是物件層通常是相同的資訊所以才能夠在系統偏好裡設定電腦自動產生索書號

12 設定系統參數

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 32: koha 2.2 使用手冊

藉由設定多種參數調整 Koha 適應個別圖書館的需要部份參數必須先設定才能啟用部份參數可以留待將來再設定先從控制圖書館作業環境的參數開始下一節再討論更複雜的

書目資料設定

121 分館

分館就是圖書館的服務點安裝時至少有一個服務點現在可以調整修正它的內容

先定義分館的類型如 一個總館五個分館則分別定義之

圖 110 編輯分館

鍵入分館的名稱地址電話等資料每個分館設定四字元內的代碼

第一次設定的分館內定為流通的圖書館換了電腦應重新設定

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 33: koha 2.2 使用手冊

圖 111 編輯分館類別

有些圖書館因為作業需要設定虛擬的分館如 裝訂中閉架中等

分館數及分館類別愈來愈多確認每個分館都屬於一個類別

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 34: koha 2.2 使用手冊

圖 112 新增分館

圖分館設定

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 35: koha 2.2 使用手冊

122 印表機

伺服器連接印表機時應分別定義該等印表機

每個印表都需設定內定印表機是lp 可以使用多個印表機各給名稱 text or color laser

圖 113 Printers screen

也可以用瀏覽器的列印功能列印 Koha 的畫面

參閱 210 使用者指列

123 館藏型式

即館藏的類別使用之前需仔細思考借書規則統計報表線上公用目錄等功能都都 依賴它而生

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 36: koha 2.2 使用手冊

圖新增館藏型式

代碼長度最多四個字元不會顯示在螢幕讀者祗看到描述費用是借閱該館藏型式時讀者需支付的錢如 光碟片的租金等可續借是讀者可以續借該館藏型式的次數無法借閱

則指定該館藏型式均不外借

本例是一般圖書可外借續借以三次為限借閱不必費用

館藏型式用處很多可控制 Koha 的工作如

讀者可指定搜尋特定的館藏型式 借閱規則可依照館藏型式及讀者類別和分館而定

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 37: koha 2.2 使用手冊

設定館藏型式是安裝之後必須的工作之一

圖館藏型式

別的設定可以稍晚再做但館藏型式必須先做 把館藏編目入館後才能進入借還書等作業

124 讀者類別

從這裡將讀者分門別類

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 38: koha 2.2 使用手冊

圖 116 讀者類別管理

財團法人佛教慈濟綜合醫院大林分院圖書館把讀者分為幾個類型 本院同仁實習同學及醫師志業體人員及師生長期借閱社區醫護人員院外來賓館合單位大林館員等八類學術圖書館可以分為 教職員(TR)圖書館員(SF)研究生(GD)大學部學生(UG)等五類公共圖書館可以分為成年人兒童圖書館員等讀者類別不是必要的設定但有助於發揮 Koha 的特性研究生的借書記錄將被連接至指導教授大學部學生的借書記錄將被連結至導師

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 39: koha 2.2 使用手冊

圖 117 新增讀者類別

從設定類別代碼開始描述每個類別的讀者型態代碼祗限兩個英文字母以內註冊有效日期係指該類型讀者的最大有效年份大學生含延畢最多八年系友可無限期則設定為99年年齡上限及年齡下限依照閱覽規則填寫若兒童借書證規定年齡是 2歲至 12歲

則分別設定之若沒有上限則可設定為 999註冊費用及預約費用依照閱覽規則填寫整 數或六位數以內的小數不使用幣別代號逾期通知需求可設為是或否告知 Koha 寄發通

125 借閱規則

館藏型式和讀者類別設定後接著設定借書規則各分館的借書規則不同也需先設定分館

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 40: koha 2.2 使用手冊

圖 118 借閱規則

借閱罰款的說明相當清楚左邊是館藏型式上方是讀者類型最上方是選擇分館每個讀者類型對每個分館的各個館藏都可以分別設定借閱期間及數量以及罰款金額起始

日數及累計日數等沒有設定的部份將依照星號空格的內定值辦理

應忽略內定值必須逐一設定所有的儲存格否則可能出現錯誤訊息

借閱儲存格有兩個數字以逗點分開第一個數字是借書期限第二個數字是借書數量研究生可借 50冊 180天 設為 18050

Koha 不接受 00的設定不想讓特定類型讀者借特定館藏型式時可以設定為 10或01 可達到同樣的效果

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 41: koha 2.2 使用手冊

罰款儲存格有三個數字以逗點區隔第一個數字是罰款金額第二個數字是逾期天數第三個數字是累計的天數若逾期每天罰兩元 逐日罰款則設為 211

罰款係由位於misc目錄內的 fines2pl計算請要求您的系統管理員設定 crontab使這個程 式在午夜後執行以便罰款能在每晚重新計算

126 停用字

這是英文等羅馬語系的在檢索目錄及建立關鍵字索引時希望 Koha 忽略的字都在這裡設定TheA 等字詞對檢索沒什麼意義的字都可以排除在外以加速效率

至少設定一個停用字否則 Koha 會當機

圖 119 英文的停用字

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 42: koha 2.2 使用手冊

熟稔MySQL 的話可以用「Load Data Infile」指令更快速容易的建立停用字表很多圖 書館公開它們的停用字表直接下載就行了

127 Z3950 伺服器

它的意思是「應用服務定義及協定規範」就是可以查詢下載其他圖書館的書目資料俗稱的複本編目或是「從國圖抓書目資料」

Koha 2xx 安裝於MS Windows 或Mac OS X 時不能使用 Z3950 客戶端這個 Bug 將於300 版修訂

Z3950 係指國際標準 ISO 23950 Information Retrieval (Z3950) Application Service Definition and Protocol Specification [應用服務定義及協定規範] 也是美國的國家標準 ANSINISO Z3950在技術層面上幾乎完全相同臺灣的中國國家標準 CNS 13461 資訊檢索服務與協

定指的是同一件事目前由美國國會圖書館負責維護

Z3950 係查詢及檢索遠端資料庫的國際標準實務上圖書館透過它查詢及檢索遠其他圖書館的書目記錄客戶端軟體通常是圖書館自動化系統的一部份伺服器端軟體較少丹麥

的 Index Data 公司提供多種使用 Z3950的軟體工具還有一個 全球的 Z3950 伺服器清單 臺灣的全國圖書資訊網(nbinetncledutw)國立政治大學中正圖書館(jendalibnccuedutw)國立臺灣大學圖書館(tulipsntuedutw) 都在名單之列

選擇支援MARC 書目格式的圖書館從 Z3950 目錄 httptargettestindexdatacom 選取使用 相同MARC 書目格式的圖書館通常是匿名簽入若需帳號密碼鍵入後Koha 會記得它

不需每次鍵入

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 43: koha 2.2 使用手冊

圖 120 Z3950 伺服器設定

不需要設定太多的 Z3950 伺服器五個足夠了六個是上限太多的伺服器反而拖累整個 搜尋的結果

128 館藏採訪基金管理

在系統偏好的採訪裡選擇標準模式就可以從這裡管制採訪預算若選擇簡單模式則略 過此節

採購預算是一個管制圖書館購書經費的科目適用於任何物品不以圖書為限圖書視聽資料期刊電子資料庫若有分別的預算科目就可以在這裡設定四個採購預科目 設定科目名稱設定預算額

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 44: koha 2.2 使用手冊

圖 121 館藏採訪基金管理

每筆科目都有代號祗能用英文字母最多五個字母通常以 BOOKSAVSRDATA 分別代表圖書視聽資料期刊資料庫若為分館的經費則設定分館

分館選項內容不受限於系統偏好分館獨立的設定

設定科目之後才能設定預算的期間及金額

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 45: koha 2.2 使用手冊

圖 122 期刊採購預算

設定預算時不可用金錢符號也不可用逗號每筆預算可以設成多個科目

先設定系統偏好的日期格式才能順利運作

129 貨幣

至少設定一個新臺幣 TWD 匯率為 1若代理商要求以外幣結匯則依照現況鍵入匯率 如美元 003078

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 46: koha 2.2 使用手冊

圖 123 貨幣

貨幣名稱最多十個字元匯率係用來計算預算的剩餘額度

1210 其他

( 請把你的建議及想法寄給 mao aT lins dOT fjuedutw 將會加到這個部份裡)

Rachel Hamilton-Williams 的意見

Koha 有兩種列印的方式視圖書館的類型而定通常祗需要其中之一

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 47: koha 2.2 使用手冊

從瀏覽器列印看到的網頁內容就像其他的網頁使用直接連結個人電腦的印表機或網路 印表機使用瀏覽器的檔案 gt 列印 gt 選擇印表機即可

使用流通功能時可以讓 Koha 列印螢幕看不到的檔案如 借書收據逾期通知Koha 自 動列印這些檔案所以伺服器需要知道這些檔案該送到什麼印表機

伺服器需要看到印表機所以必須是網路印表機或直接連到伺服器的印表機不論何種方法Koha 要知道印表機的路徑不可能每次從對話盒去設定路徑

不辦理流通業務就不需要設定網路印表因為所有的自動列印都與流通有關

3 設定書目資料參數

在系統偏好管理的館藏目錄裡設定變數 marc 為 1 時表示使用MARC 書目資料接下來 就要設定複雜而重要的參數各種MARC 有互異的規則以欄位方式標示其內容Koha 可

以使用多種MARC 所以需告知 Koha 處理特定MARC 資料的方法Koha 使用特別的MARC 工具簡化煩瑣的日常編目作業但需先設定參數才能用它們

設定書目資料參數很囉唆多留些時間在編目員的協助下設定它們否則就要熟稔MARC 編目作業後再來設定它們有關MARC 21 的背景及原則參見httpwwwlocgovmarc96principlhtml 詳細的書目資料欄位參見httpwwwlocgovmarcbibliographicecbdhomehtml 有關 UNIMARC 的事宜參見 httpwwwiflaorgVI3p1996-1sec-unihtm

本使用手冊不解說MARC 應先熟悉MARC 的欄位分欄指標等資料才能閱讀本 節的資料

131 機讀編目格式書目架構 - 初體驗

彈性是 Koha 的基本原則使用者可以完全掌控 Koha 在MARC 方面亦復如此使用者有三個選擇 不用MARC 採用MARC 21 採用 UNIMARC(CMARC)使用者必須精準的告

訴 Koha 顯示MARC 資料的方式連結MARC 資料至 Koha 資料庫的方法

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 48: koha 2.2 使用手冊

書目記錄架構允許使用者定義多種顯示架構以新增MARC 資料入 Koha首先定義使用 到的MARC 欄位及忽略的欄位

安裝的時候可以選擇下載採用MARC 21 或 UNIMARC(CMARC) 資料或者不用任何MARC 資料庫順利安裝後就可以使用指定的MARC 格式在書目架構管理頁面選定MARC 的欄位告訴 Koha 在每個架構裡使用適當的欄位

圖 書目架構

至少有一個預設書目架構點選機讀格式(MARC) 結構本手冊採用 CMARC 的範例

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 49: koha 2.2 使用手冊

圖預設書目架構的欄位管理

這個畫面有六個欄位 欄位標籤可重複必要容許值分欄等

The columns on this screen contain the tag number the name of the tag (Lib is an abbreviation of the French word libelleacute) whether or not the tag is repeatable (according to the rules of your chosen MARC dialect) whether or not you want the tag to be mandatory (according to your librarys cataloging practice) columns for authorised values and editing subfields (both of which we will discuss elsewhere) an edit icon and a delete icon A pull-down menu at the top of the page allows you to switch between your biblio frameworks and a search box next to it allows you to skip to a specific tag

If you are certain that you will never use a MARC tag then you can delete it but since this will not result in any appreciable improvement in performance it is probably better to leave it There will be tags you want to add however (The Add Tag button is at the bottom of the screen and cannot be seen in the screenshot above) If you are using older MARC tags that are not in the list of tags supplied with Koha then use this page to add them Similarly you will probably need to add the holdings tag you currently use or at least check the subfield structure of the 852 tag if you use it for holdings

If you click on the edit icon you will be able to change the values for each MARC tag

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 50: koha 2.2 使用手冊

Figure 126 Editing MARC Tags

The values that can be changed on this screen are the name of the tag as it will be displayed in the librarians interface (Lib for librarians) the name of the tag as it will be displayed in the OPAC whether or not the tag can be repeated within a MARC record whether or not it is mandatory and finally a pull-down menu (initially empty) of Authorised values Since this is a feature that is not commonly found in an ILS cataloging system now is a good time to interrupt the process of defining the biblio frameworks and discuss Authorised Values

Tip

You can define biblio frameworks without defining any authorised values but if you wish to make full use of Kohas features you will probably define authorised values as part of the process of defining the biblio frameworks moving back and forth from the Biblio Framework screens to the Authorised Values screens

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 51: koha 2.2 使用手冊

32 Authorised Values

Koha allows you to restrict the values that catalogers can place in some MARC tag indicators and MARC subfields allowing only certain pre-defined authorised values These authorised values are defined here

Figure 127 Authorised Values Administration

As an example let us assume that your Koha installation is used by several libraries and you use MARC 21 You might want to restrict the 850a MARC subfield to the institution codes for just those libraries In that case you could define an authorised values category (perhaps called INST) and enter the institution codes as the authorised values for that category (By the way category names are limited to eight characters)

Once the 850a subfield is linked to the INST authorised values category in your MARC tag structure catalogers must choose a value from the list you define here and may not type in any other value In other words the catalogers could not type in the 850a field but instead would see a pull-down menu If the INST category was setup as it is in the screenshot above then the pull-down menu would have two choices Athens County Library System and Nelsonville Library

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 52: koha 2.2 使用手冊

Depending on which of these the cataloger chose Koha would insert the appropriate authorised value into the MARC record -- ONe if the choice were Nelsonville Library for example

Koha automatically sets up authorised value categories for your item types and branch codes and you can link these authorised values to MARC subfields when you set up your MARC tag structure

To go back to our discussion of editing MARC tags in the Biblio Frameworks the authorised value allowed for a tag is the tag indicator pair Many tags in MARC 21 should have both indicators set to the undefined character () so you could make an authorised values category called indicatr and enter an authorised value of as the only entry Then you could select the indicatr authorised value category when editing one of the tags that require undefined indicators The real power of authorised values however is demonstrated when they are used with MARC subfields So lets go back now to our MARC tag structure and look at the MARC subfields

Note

Currently (in Koha version 223) the Authorised Values feature for tags is not functional -- it only work with MARC subfields In some future version this feature may be fixed but if it proves to have only limited usefulness it may also be dropped from Koha

33 Biblio Framework (MARC Structure) -- subfields

The MARC subfield structure that you define will determine how Koha behaves for your catalogers Needless to say it is probably a very good idea to involve them in this part of the parameterization of your Koha installation

To edit MARC subfields navigate to the MARC tag structure administration screen and click on the subfields button In our examples we will start by clicking on the subfields button associated with MARC 21 tag 100 MAIN ENTRY--PERSONAL NAME

Figure 128 Subfield structure for tag 100

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 53: koha 2.2 使用手冊

As you can see most of the subfields are ignored in this particular Koha installation Subfield 100a however has quite a few constraints If we move to the bottom of this screen we find an icon of a folder opening Click on this icon to open the subfield editing screen to see what the possible subfield constraints are and how to change them

Figure 129 Tag 100 subfields (editing)

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 54: koha 2.2 使用手冊

The subfield editing screen is very busy with a lot of features that are unique to Koha We will examine each of these

The screen displays all of the subfields that can be used with a tag so it can be quite long (as in this case) Looking at the section for Tag 100 Subfield a we first see a group of MARC constraints These determine how the information in the subfield is to be used by Koha The repeatable and mandatory checkboxes will allow catalogers to repeat a subfield or will cause Koha to issue an error warning if the cataloger leaves a mandatory subfield empty Search also is an interesting feature that allows a catalogue search to check several MARC subfields at the same time In this example a catalogue search for a certain author will check first for the authors name in subfield 100a of all MARC records but will also check in 700a (in case the name is an added entry) and in 110a and 710a (in case the author is an organization) You could add more subfields here -- perhaps 511a in case the author is actually a performer -- by typing them in the text field enclosing each subfield identifier in single quotes and separating them with commas

Note

The parenthetical example for 200a refers to UNIMARC tag numbers

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 55: koha 2.2 使用手冊

The Koha link constraint requires some background explanation Koha was originally written without any provision for using MARC records and may still be used without MARC records This is possible because the original Koha keeps basic bibliographic data in database tables and fields that were designed by the original developers of Koha Since the time when MARC capability was added to Koha the developers have referred to these tables and fields as the original Koha database and called the MARC records and MARC structural data the Koha MARC database Many of the simple tasks and searches that a library performs in the process of checking books in and out are still more efficiently managed by the original Koha database So as you are building your MARC structure you must tell Koha which MARC subfield data should be automatically loaded into the original Koha database or Koha will not work

When you fill in the Koha link constraint you choose from a pull-down list of all the tables and fields in the original Koha database presented in the form tablefield The table names are not that important for purposes of establishing your Koha links the field names should be sufficient to help you decide which links are appropriate Only one MARC subfield can be associated with an original Koha field This means two things 1) you must use the Search also constraint if you want simple searches to look in more than one MARC subfield as we have with MARC tag 100a and 2) most of your MARC subfields will not be linked to an original Koha field -- there are many more MARC subfields than original Koha fields

The Editor constraints section mostly controls how this subfield is presented to the catalogers The Text for librarian and Text for OPAC will be the descriptive name of this subfield in the librarians interface and the public catalogue respectively The Managed in tab constraint allows you to choose from a pull-down list with the values ignore numbers 0 through 9 and items (10) Tab is not the keyboard tab used for indenting text in this case tab refers to a tab like you would find on a manila file folder or in a web browser that supports tabs It allows you to subdivide the MARC tags and subfields the catalogers will be using into several browser tabs so the cataloging web page will not be too long Ignored subfields simply do not appear at all while subfields managed in tab 0 will appear in the first tab subfields managed in tab 1 will appear in the second tab etc (Numbering things beginning with 0 instead of 1 is a convention of computer programming) For instance you might choose to put all of the MARC subfields associated with the MARC 21 number and classification tags 010 to 088 (except for the subfields you want to ignore) in tab 0 all main entry tag subfields (tags 100-130) in tab 1 etc This will keep the cataloging web page more manageable

Note

Koha currently does not use data from any MARC tags below 010 but you can define tags below 010 and use them to store data from imported MARC records Koha can also calculate a Leader for your MARC records -- see the section on plugins for more information

See the related comments in the User Comments section

The items (10) tab is reserved for subfields that only contain item information The items information appears on a separate screen from the rest of the basic MARC bibliographic record in Koha since items are managed separately from the rest of the bibliographic record libraries routinely add or delete item information from MARC bibliographic records as extra copies of library materials are added or removed from the collection

Koha requires that one -- and only one -- MARC tag will be linked to the original Koha items table Some of the fields in the items table are meant to hold data indicating the current status of an item and will not be linked to the MARC record Other important data will come from your MARC

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 56: koha 2.2 使用手冊

holdings tag itemsbarcode itemsdateaccessioned itemshomebranch itemsprice and itemsitemcallnumber are good examples So whatever MARC tag you use for your holdings information (whether it be 852 or 9xx or whatever) should be managed in tab items (10) -- and that should be the only MARC tag managed in that tab -- and it should be linked to the appropriate fields in the original Koha items table -- and be the only MARC tag linked to the items table If you manage more than one MARC tag in the items tab or link more than one MARC tag to the items table Koha will not work

The hidden and URL checkboxes have pretty clear on-screen explanations If the hidden box is checked the subfield will be used by Koha but never seen by the catalogers Instead of manually filling such a subfield Koha will follow instructions from the default options to fill the subfield The URL checkbox simply tells Koha that the content of this subfield should appear as an active hyperlink when the record is displayed in the catalogue

The Default Options section allows you to use several unique features of Koha to fill subfields with default values We will look closely at each of these features in the next sections None of these options must be used -- they are truly optional -- but they can make some of your cataloging chores simpler Note the warning on the screen -- you cannot choose to use more than one type of default option for a given subfield

Once you have completed editing your subfields you will have completed the most difficult and time-consuming part of preparing Koha for use You are almost done

331 Authorised Value

We have already discussed authorised values in the context of MARC tags but their most important use is with subfields instead of tags If you choose a category of authorised value from the pull-down list then the only values that the catalogers can enter into this subfield will be values they choose from that category Even if you have not defined any authorised value categories you will have two automatic pull-down choices branches and itemtypes You can prevent the catalogers from manually entering branch codes and item types in subfields of your holdings tag by choosing one of these authorised value categories

For example as you are setting the structure for your holdings tag you can set up a subfield meant to contain the branch location of an item so that it pulls an authorised value from the branches category Then as catalogers are adding holdings to your catalogue they will find a pull-down list of all your branch names in this subfield they will only be able to choose a name from this list and cannot type in anything else If you also link this subfield to itemshomebranch or itemsholdingbranch you will always be able to accurately track an items location

Note

You must use the itemtypes authorised values for at least one of your MARC subfields and then link that subfield to biblioitemsitemtype

You must have two subfields in your MARC holdings tag that use the branches authorised values and those two subfields must be linked to itemshomebranch and itemsholdingbranch (The holding branch value in the items table will change as an item is transferred from branch to branch but it still must have an initial value set when an item is cataloged)

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 57: koha 2.2 使用手冊

332 Thesaurus

Kohas thesaurus feature is a way to use MARC authority records -- not to be confused with Kohas authorised values -- to make sure only standardized names titles etc are used in your catalogue records There will be much more detailed discussion of authority records in a later section (Thesaurus Structure) this section will provide only a basic overview of how to activate this feature

If you wish to provide access to authority records for a given subfield -- MARC 21s 700a subfield for instance to make sure an authors name is available in an added entry in its approved form -- you will need to create a subfield 9 for that tag (eg tag 700 subfield 9) by adding it at the end of the subfield editing screen

Figure 130 Adding subfield 9

Koha uses subfield 9 to store the link between a bibliographic record and an authority record Make sure this subfield is managed in the same tab as the other managed subfields for this tag and then click the hidden checkbox so it will not be displayed with the rest of the record

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 58: koha 2.2 使用手冊

Go to the subfield that will hold the value you want to standardize (eg 700a in MARC 21 for an authors name) For this subfield choose an appropriate thesaurus category (that you have created in your Thesaurus Structure) from the pull-down menu -- perhaps category PN (Personal Name)

Now when the catalogers are adding a record they will see three dots () after the textbox of the 700a subfield Clicking on these dots will open a pop-up window allowing the cataloger to search your authority records for a standardized version of the authors name If the desired name is found in your authority records it can be automatically copied into the 700a subfield (If the desired name is not found the cataloger can enter the name manually)

333 Plugins

Plugins are small computer programs (Perl scripts to be exact) which can be used to calculate the value of a subfield To date most plugins that are available as part of the Koha code deal with UNIMARC fields but a programmer could create a custom plugin to do anything you want

For example you might want to create a plugin that would take the MARC 21 Library of Congress Control Number (subfield 010a) add your organization code to the beginning add a cataloger-defined character at the end and save the result as your System Control Number (035a) A programmer could create this plugin for you name it something like control_numberspl and save it with your other Koha code Then as you are editing your MARC 21 subfield 035a you could choose the control_numberspl plugin from the pull-down list

Tip

The Koha plugins are stored in your Koha intranetcgi-bin directory in the subdirectory value_builder

Now (in our theoretical example) when the catalogers are adding a record they would see three dots () after subfield 035a Clicking on these dots would open a pop-up window that asks the cataloger to enter the special character to be added to the end of the LC Control Number the plugin would then use the value already entered in 010a your organization code and the special character to construct the System Control Number and insert it into the subfield The cataloger would always have the option of changing this value or simply entering the System Control Number manually instead of using the plugin

334 Leader plugins

Beginning with version 224 Koha comes with special plugins for building Leader information for MARC records

The Leader is a fixed field at the beginning of each MARC record that contains coded information for the processing of the record It does not have a number as the other MARC tags do -- it is simply the Leader

Koha has no need for Leader information and does not use it However Koha can store Leader data and can help you build your own Leader data Here is how

When setting up your Biblio Framework add a tag 000 and call it Leader (or whatever you wish to call it)

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 59: koha 2.2 使用手冊

In this 000 tag create a subfield and name it leader (or something) This subfield will be the subfield that stores the Leader data If you are importing MARC records directly into Koha you can now store the Leader in this 000 tag and subfield If you wish Koha to help you build Leader data for MARC records you create with Koha select the plugin marc21_leaderpl (for MARC 21) or unimarc_leaderpl (for UNICODE) for the subfield

When you create (or edit) bibliographic records clicking on the three dots following the tag 000 field will open a pop-up window to guide you through the creation of your MARC Leader

Figure 131 Leader pop-up window

Make the appropriate choices from the pull-down menus and Koha will create the encoded Leader data and insert it into your 000 subfield You now have Leader data stored with your records should you ever need it for some other application

335 Link

A link is somewhat like a simplified plugin If you have two MARC subfields that will always contain the same value -- for example the two subfields in your holdings tag that will store home branch and holding branch for a system that has only one branch -- then you can link the second subfield to the first and the value will be automatically entered into the second subfield as you enter it in the first

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 60: koha 2.2 使用手冊

34 Koha to MARC Database Links

This page provides a simplified way to map your MARC tags and subfields to the original Koha database tables This can also be done while setting the MARC tag structure as we have seen but it is easier to see the relationship between the MARC database and the Koha database here

Figure 132 MARC to original Koha links

The pull-down menu at the top lists all the Koha tables that can receive values from the MARC records The columns from each table are listed in the area below the pull-down menu Do not expect to have every Koha tablecolumn mapped to a MARC subfield Some (such as biblionumber biblioitemnumber and itemnumber) are values generated by Koha and will probably be automatically mapped Others are flags which are set in the course of normal circulation activities and will contain information that is not part of your MARC record

This is a one-to-one mapping In other words a MARC tagsubfield can be mapped to one and only one Koha tablecolumn MARC data that is not mapped to a Koha table does not disappear -- it is simply not available for display on circulation screens and on some search results screens

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 61: koha 2.2 使用手冊

35 MARC Check

Once you have completed the process of setting up your default Biblio Framework (MARC structure) and have reviewed your Koha-MARC links click on this link to activate a small program that checks for major errors in your MARC setup

Figure 133 Checking MARC setup

This MARC check does not guarantee that you will like the first results of your efforts to set up your MARC displays etc -- it simply checks for major errors You will probably revise your MARC setup several times before you are completely pleased with it Be sure to run this program after every revision

36 Thesaurus Structure

Catalogers often rely on MARC authority records to keep personal names place names subjects etc standardized across a catalogue For example if you have several books by the late Pope in your collection the bibliographic records you import from other sources may have the authors name in a variety of forms John Paul II Pope 1920-2005 or Joannes Paulus II Pope 1920-

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 62: koha 2.2 使用手冊

2005 or Juan Pablo II Pope 1920-2005 or Jean Paul II Pope 1920-2005 or Johannes Paul II Pope 1920-2005 or Joann Pavel II Pope 1920-2005 to name some of the many possibilities But you want all of the books to be displayed whenever a catalogue user searches for John Paul II To do this you modify the bibliographic records so they conform to an authority record that specifies the correct form of the name as John Paul II Pope 1920-2005

Individual catalogers almost never create their own database of authority records but instead buy or download authority records from a trusted source These authority records have their own MARC structure which looks somewhat like a simplified MARC bibliographic record structure If you have access to such a database you can setup Kohas Thesaurus Structure to allow you to retrieve values from the authority records as you create or modify your bibliographic records

When you select Thesaurus structure from the Koha parameters page you will see this screen at first

Figure 134 Thesaurus administration (unchanged)

The Koha installation process offered the opportunity to install a default authority record framework for MARC 21 or UNIMARC If this was done you can click on the MARC structure

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 63: koha 2.2 使用手冊

button for the Default framework and see the structure that has been setup for your authority records

Figure 135 Authority record structure (MARC 21)

If you are using a different flavor of MARC you will need to define the authority record structure manually or modify the MARC 21 or UNIMARC structure to conform to your MARC flavor The SQL statements to create the default framework if it was not created during the installation process are stored in your Koha intranet directory in the sub-directory scriptsmiscsql-datas Otherwise you should have no need to modify any of the default framework unless you intend to create your own authority records

You now need to define some authority types by clicking on the Add authority type button at the bottom of the administration screen As an example we will set up an authority type to be used for personal names using MARC 21 authority and bibliographic tags

Figure 136 Personal name authority type

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 64: koha 2.2 使用手冊

The Authority type box accepts a code for this authority type For personal names you could use PN The Description is the term that will appear in some pull-down menus and is purely for information -- in this case it explains what PN means

The Summary textbox holds the list of authority record subfields which will be displayed when the cataloger accesses the authority records to look for a match for a personal name in a bibliographic record (Displaying the entire authority record would result in a display that would be too big to be useful) Each subfield should be enclosed in square brackets In our example a search of the authority records for a personal name will display the MARC 21 personal name heading tag (100) using both the subfields that hold the regular form of the name (100a) and any fuller version of the name (100q) The search will also display the see from tracing tag (400) and the see also tracing tag (500) (For personal names in UNIMARC you might use [200a][200b][200c] [400a][400z] [100a]) The display of the summary of the authority records in the search results list would thus contain the heading field the see from tracing fields and the see also tracing fields

Note

You might also consider setting up the display to give you more information such as adding subfields 100b 100c and 100d to the list so you can see more information about an author If you

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 65: koha 2.2 使用手冊

include all of these subfields on the same line with your 100a subfield in the Summary box they will appear on the same line in your search display

The Report tag is the authority tag from which a value will be retrieved and reported back to the bibliographic record when the cataloger selects an authority record from a search results list

Our Thesaurus Structure screen now looks like this

Figure 137 Thesaurus administration (modified)

You can continue to add other authority types for place names organization names etc The code for every authority type you define will automatically appear in the Thesaurus pull-down list when you setup your Biblio Frameworks

To follow along with our example let us assume that you have a database of authority records you have defined a PN authority type as above and have defined a (MARC 21) Biblio Framework with a subfield 9 defined (for holding the link to an authority record) and with the Thesaurus value for subfields 700a 700b 700c and 700d set to PN In your authority records database you have the following record 040 $b eng

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 66: koha 2.2 使用手冊

100 0 $a John Paul $b II $c Pope $d 1920-2005400 0 $a Joannes Paulus $b II $c Pope $d 1920-2005400 0 $a Juan Pablo $b II $c Pope $d 1920-2005400 0 $a Jean Paul $b II $c Pope $d 1920-2005400 0 $a Johannes Paul $b II $c Pope $d 1920-2005400 0 $a Joann Pavel $b II $c Pope $d 1920-2005510 2 $a Catholic Church $b Pope (1978-2005 John Paul II)700 04 $a Juan Pablo $b II $c Papa $d 1920-2005 $7 aacrspa700 06 $a Jean Paul $b II $c pape $d 1920-2005 $7 aacrfre700 04 $a Jean Paul $b II $c (Pape) $d 1920-2005 $7 ncafnor700 04 $a Johannes Paul $c Papst $b II $7 rak

The cataloger is working with a bibliographic record for a book written by Joannes Paulus II Pope 1920-2005 and wants to add an entry to the bibliographic record with the authorized version of the name in English The cataloger would go to the 700a subfield in the bibliographic record and click on the three dots () that appear after the subfield because this subfield has thesaurus access enabled A search box pops up and the cataloger can perform a search for the name as it appears in the bibliographic record to find any matching entries in your authority records

Figure 138 Authority record search

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 67: koha 2.2 使用手冊

Clicking on the curved arrow in the Get It column will retrieve the values in the authority record and insert them into your bibliographic record Any of your subfields which have the thesaurus option enabled will be modified with the values in the Report tag you set up in your Thesaurus Structure In our example we asked for the contents of tag 100 to be reported and we enabled the thesaurus option for subfields 700a 700b 700c and 700d So clicking on the arrow inserts the value from 100a into 700a 100b into 700b etc Not only that but because the 700 tag in this particular bibliographic record is now linked to this particular authority record (through subfield 9) this bibliographic record will be automatically modified if this authority record is ever modified

Establishing an effective link between authority records and bibliographic records will require that you spend a lot of time working back and forth between your Thesaurus Structure and your Biblio Frameworks But for libraries that have a database of authority records the thesaurus is a very powerful cataloging tool

37 - User comments -

(Send comments and remarks to ltsthedges AT gmail DOT comgt They will be added to this section)

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 68: koha 2.2 使用手冊

Posted by Thomas Dukleth

Fixed fields and control fields without subfields can be created in the Koha MARC frameworks by creating a field with whatever field name is needed and creating a subfield with as the subfield identifier Koha will treat these special subfields as fields without indicators even if the record editor shows unused blank phantom indicators The leader is field 000 with subfield If fields 000 to 008 are missing from Koha MARC frameworks the user can add them along with any other omissions in the Koha framework editor in Koha System Administration

Fields and their subfields will appear in the MARC views and the record editor if their subfields or pseudo subfields are set to managed by Koha in the MARC framework editor To have them appear in the detail view requires editing the templates Subfield order will be simple alphabetic order unless you hack Koha significantly or wait for version 30

Collective field indexing can be provided for any fieldsubfield by providing field and subfield linking in the search also text box in the MARC framework editor This collective field linking is not compliant with searching several indexes separately in accordance with the structure of the bibliographic record but it is much faster Record indexing will run from a different database design in version 30

2 線上公用目錄

流通

採錄及編目

期刊

報表

定期維護

資料庫結構 翻譯

參考書目

Koha 22 Users Guide Using the Power of Free and Open Source Software for Library Management Stephen Hedges Joshua Ferraro and others 2006 httpwwwkohadocsorgusersguide

2000 年各層級圖書館資訊系統軟硬體規範書httpcatwebncledutw2-1-19htm

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -
Page 69: koha 2.2 使用手冊

GNU 通用公共許可證 一九九一年六月第二版 httpwwwlinuxorgtwCLDPOLDdocGPLhtml 譯自 httpwwwgnuorgcopyleftgplhtml

Koha Users Around the Worldhttpwikikohaorgdokuphpid=kohausers

  • Koha使用手冊
    • Tip
    • 32 Authorised Values
    • Note
    • 33 Biblio Framework (MARC Structure) -- subfields
    • Note
    • Note
      • 331 Authorised Value
        • Note
          • 332 Thesaurus
          • 333 Plugins
            • Tip
              • 334 Leader plugins
              • 335 Link
                • 34 Koha to MARC Database Links
                • 35 MARC Check
                • 36 Thesaurus Structure
                • Note
                • 37 - User comments -