This patch adds the relator code gdv (Game developer) in the list of
MARC21 relator terms in Koha.
To test:
1. Apply patch and reset_all
2. Go to Administration > Authorized values > RELTERMS
3. Search for gdv
--> The new relator code should be there with its corresponding term
"Game developer"
Note: this is added in the installer files. It will not affect existing
installations. For existing installations, add the new relator code in
Administration > Authorized values > RELTERMS.
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
This patch updates the default MARC21 framework to reflect the changes
brought by Update 37 (December 2023).
To test:
1. Apply patch and reset_all
2. Go to Administration > MARC bibliographic framework
3. Click Actions next to the default framework and choose MARC structure
4. Check for the changes detailed in the update
https://www.loc.gov/marc/bibliographic/bdapndxg.html
- Two subfields of 022 should be marked as obsolete
- l ISSN-L [OBSOLETE]
- m Canceled ISSN-L [OBSOLETE]
- There should be a new field 023, named CLUSTER ISSN
- This field should be repeatable
- Subfields:
- 0 Authority record control number or standard number (NR)
- 1 Real World Object URI (R)
- 2 Source (NR)
- 6 Linkage (NR)
- 8 Field link and sequence number (R)
- a Cluster ISSN (NR)
- y Incorrect Cluster ISSN (R)
- z Canceled Cluster ISSN (R)
- There should be one new subfield in field 532
- 3 Materials specified (NR)
5. Optional: run the framework test in Administration > MARC
bibliographic framework test
--> All should be OK
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
This patch adds the appropriate table classes to the Popup html
customisation block. This ensure we have proper table display formatting
in the modal on the OPAC.
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Victor Grousset/tuxayo <victor@tuxayo.net>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
This patch adds some default html customisation content for the cookie
consent feature.
Test plan
1) Run through the installer and pick to import the sample news items
2) Confirm that after enabling the CookieConsent preference that the
default content appears in the cookie bar at the bottom of the page
and in the modal that appears after clicking 'More information'
Mentored-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Victor Grousset/tuxayo <victor@tuxayo.net>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
This patch corrects the default UNIMARC bibliographic framework to
place all the 4XX subfields in tab 4.
To test:
1. Go to Administration > MARC Bibliographic framework test
--> There should be errors indicating subfields from 4XX fields
are in tabs 3 and 4
2. Apply patch and reset_all
3. Redo step 1
--> It should now say that all subfields for each tag are in the
same tab (or ignored)
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Victor Grousset/tuxayo <victor@tuxayo.net>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
A HOLDPLACED notice exists and is used by the emailLibrarianWhenHoldIsPlaced function, but libraries may want to use different wording when emailing patrons.
Signed-off-by: Kelly <kelly@bywatersolutions.com>
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
The first patch highlighted a minor inconsistency to me and this patch
just brings us closer to html5 consistency throughout the notices by
replacing any existing occurences of `<br />` and `<br/>` with the
recommended `<br>`.
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
When a notices is marked as HTML, we need to use block elements
(p, div, li, etc.) or explicit line breaks.
This adds the line breaks where required.
Affects:
* ISSUEQSLIP
* ISSUESLIP
* TRANSFERSLIP
* CHECKINSLIP
* HOLD_SLIP
* WELCOME
The biggest change is the WELCOME notices. With this patch
it appears no longer on only one line, but properly formatted.
To test:
WELCOME
* Without patch
* Make sure your Koha can send email (set up SMTP server, KohaAdminLibraryAddress)
* Make sure your patron has an email set
* In patron account, use "More > Welcome email"
* Verify all text is on one line
* Apply patch
* reset_all to install new sample notice templates
* Repeat test, verify welcome notice is now nice
ISSUESLIP, ISSUEQSLIP
* Checkout at least 2 items
* Print > Print slip
* Print > Print quick slip
* Verify both look nice!
CHECKINSLIP
* Return both items
* Print checkin slip (button in list of checkouts)
* Verfiy... you know, that it looks nice!
TRANSFERSLIP
* Checkin an item from another library
* "Print transfer slip"
* Verify again.
HOLD_SLIP
* Place a hold on a record
* Return an item that can fill the hold
* "Print slip and confirm"
* Verify.
* Note: if you compare to before, this also removes a <> appearing instead
of the city.
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Some notices had the is_html flag for new installations, but actually
didn't include any HTML formatting. These should be plain text
to have the line breaks behave as expected.
This updates:
* 2FA_OTP_TOKEN
* OPAC_REG_VERIFY
We cannot do a database update here, as libraries will
have changed and updated these. So this is only for new
installations.
To test:
* Apply patch
* reset_all (create a new sample database)
* Verify that the HTML checkbox is not set for these notices
* Verify they appear as plain text notices, not including HTML tags
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Victor Grousset/tuxayo <victor@tuxayo.net>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
(cherry picked from commit 338ae09e692420fe783da1699386b14891af62ab)
Signed-off-by: Jessica Zairo <jzairo@bywatersolutions.com>
Signed-off-by: Michaela Sieber <michaela.sieber@kit.edu>
Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
In HTML notices we don't need to explicitly use <html></html>.
This removes them from the 2 notices using them:
* PASSWORD_RESET
* STAFF_PASSWORD_RESET
To test:
* Apply patch
* Make sure your Koha can send email (set up SMTP server, KohaAdminLibraryAddress)
* Make sure your patron has an email set
* In patron account, use "More > Send password reset"
* Log out
* In the OPAC, request password reset ("forgot your password?")
* Verify both notices appear nicely formatted (line breaks, bold, etc.)
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch updates Koha::Checkout->attempt_auto_renew to renew when the 'final' errors are passed, and to pass the error value back to the cronjob for processing
The sample notice for AUTO_RENEW and AUTO_RENEW_DGST are both updated to handle the new error
On the next cron the error will be updated to too_many or too_unseen, but a notice will not be sent.
To test:
0 - Run reset_all to install the updated sample notices or copy the text
1 - Set system preference UnseenRenewals to 'Allow'
2 - Setup a circ rule to allow 2 renewals, 2 unseen renewals
3 - Checkout an item to a patron who has an email defined and auto renewals selected in messaging preferences
4 - Update the issue to be due/overdue:
UPDATE issues SET date_due=DATE_SUB(NOW(), INTERVAL 1 DAYS);
5 - perl misc/cronjobs/automatic_renewals.pl -v -c
6 - Confirm patron notified and issue renewed
7 - Set issue due/overdue again
8 - perl misc/cronjobs/automatic_renewals.pl -v -c
9 - Confirm patron notified of final unseen renewal
10 - perl misc/cronjobs/automatic_renewals.pl -v -c
11 - Confirm issue not renewed, patron not notified
12 - Update circ rules t all 4 renewals total
13 - Force renewal on staff side to clear unseen
14 - perl misc/cronjobs/automatic_renewals.pl -v -c
15 - Confirm patron notified of final renewal (allowed 4, 2 unseen from cron, 1 manual, this unseen from cron)
16 - perl misc/cronjobs/automatic_renewals.pl -v -c
17 - Confirm patron not notified, issue not renewed
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Test Plan:
1) Apply this patch
2) Run updatedatabase.pl
3) Restart all the things!
4) Enable the new digest option for "Hold filled" messages
5) Trap multiple holds for a patron
6) Note a single notices is generated for all the trapped holds!
Signed-off-by: George Williams <george@nekls.org>
Signed-off-by: Laura ONeil <laura@bywatersolutions.com>
Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Sponsored-by: Rijksmuseum, Netherlands
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Test plan:
Run new install or upgrade.
Check for this notice under Tools/Notices.
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Lucas Gass <lucas@bywatersolutions.com>
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
[EDIT] Enrollment fee via object instead of substitute hash.
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch updates the default MARC21 framework to reflect the changes brought by Update 36 (June 2023).
To test:
1. Apply patch and restart
2. Go to Administration > MARC bibliographic framework
3. Click Actions next to the default framework and choose MARC structure
4. Check for the changes detailed in the update https://www.loc.gov/marc/bibliographic/bdapndxg.html
- There should be one new subfield in field 041
- 3 Materials specified (NR)
- There should be a new field 361, named STRUCTURED OWNERSHIP AND CUSTODIAL HISTORY
- This field should be repeatable
- Subfields:
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- 3 Materials specified (NR)
- 5 Institution to which field applies (NR)
- 6 Linkage (NR)
- 7 Data provenance (R)
- 8 Field link and sequence number (R)
- a Name (NR)
- f Ownership and custodial history evidence term (R)
- k Formatted date (NR)
- l Date (NR)
- o Type of ownership and custodial history information (R)
- s Shelf mark of copy described (NR)
- u Uniform Resource Identifier (R)
- x Nonpublic note (R) **This should not be visible in the OPAC
- y Identifier of the copy described (NR)
- z Public note (R)
- There should be three new subfields in field 653
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- 5 Institution to which field applies (NR)
- There should be two new subfields in field 658
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- There should be four new subfields in field 720
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- 5 Institution to which field applies (NR)
- 7 Data provenance (R)
- There should be a new field 857, named ELECTRONIC ARCHIVE LOCATION AND ACCESS
- This field should be repeatable
- Subfields
- 2 Access method (NR)
- 3 Materials specified (NR)
- 5 Institution to which field applies (NR)
- 6 Linkage (NR)
- 7 Access status (NR)
- 8 Field link and sequence number (R)
- b Name of archiving agency (NR)
- c Name of Web archive or digital archive repository (NR)
- d Date range of archived material (NR)
- e Data provenance (R)
- f Archive completeness (NR)
- g Persistent identifier (R)
- h Non-functioning Uniform Resource Identifier (R)
- l Standardized information governing access (R)
- m Contact for access assistance (R)
- n Terms governing access (R)
- q Electronic format type (R)
- r Standardized information governing use and reproduction (R)
- s File size (R)
- t Terms governing use and reproduction (R)
- u Uniform Resource Identifier (R)
- x Nonpublic note (R)
- y Link text (R)
- z Public note (R)
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch updates the default MARC21 framework to reflect the changes brought by Update 35 (December 2022).
To test:
1. Apply patch and restart
2. Go to Administration > MARC bibliographic framework
3. Click Actions next to the default framework and choose MARC structure
4. Check for the changes detailed in the update https://www.loc.gov/marc/up35bibliographic/bdapndxg.html
- There should be one new subfield in field 856
- g Persistent identifier (R)
- Subfield h should now be named Non-functioning Uniform Resource Identifier
- Subfield q should now be repeatable
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch updates the default MARC21 framework to reflect the changes brought by Update 34 (July 2022).
To test:
1. Apply patch and restart
2. Go to Administration > MARC bibliographic framework
3. Click Actions next to the default framework and choose MARC structure
4. Check for the changes detailed in the update https://www.loc.gov/marc/up34bibliographic/bdapndxg.html
- There should be one new subfield in field 041
- 7 Data provenance (R)
- There should be one new subfield in field 082
- 7 Data provenance (R)
- There should be one new subfield in field 083
- 7 Data provenance (R)
- There should be one new subfield in field 084
- 7 Data provenance (R)
- There should be one new subfield in field 100
- 7 Data provenance (R)
- There should be one new subfield in field 110
- 7 Data provenance (R)
- There should be one new subfield in field 111
- 7 Data provenance (R)
- There should be one new subfield in field 130
- 7 Data provenance (R)
- There should be one new subfield in field 210
- 7 Data provenance (R)
- There should be one new subfield in field 240
- 7 Data provenance (R)
- There should be one new subfield in field 245
- 7 Data provenance (R)
- There should be one new subfield in field 246
- 7 Data provenance (R)
- There should be one new subfield in field 247
- 7 Data provenance (R)
- There should be one new subfield in field 250
- 7 Data provenance (R)
- There should be one new subfield in field 255
- 7 Data provenance (R)
- There should be one new subfield in field 256
- 7 Data provenance (R)
- There should be one new subfield in field 264
- 7 Data provenance (R)
- There should be one new subfield in field 300
- 7 Data provenance (R)
- There should be one new subfield in field 335
- 7 Data provenance (R)
- There should be one new subfield in field 336
- 7 Data provenance (R)
- There should be one new subfield in field 340
- q Reduction ratio designator (R)
- Subfield f should now be named Reduction ratio value
- There should be one new subfield in field 348
- 7 Data provenance (R)
- There should be one new subfield in field 370
- 7 Data provenance (R)
- There should be one new subfield in field 377
- 7 Data provenance (R)
- There should be one new subfield in field 380
- 7 Data provenance (R)
- There should be one new subfield in field 381
- 7 Data provenance (R)
- There should be one new subfield in field 382
- 7 Data provenance (R)
- There should be one new subfield in field 383
- 7 Data provenance (R)
- There should be one new subfield in field 384
- 7 Data provenance (R)
- There should be one new subfield in field 385
- 7 Data provenance (R)
- There should be one new subfield in field 386
- 7 Data provenance (R)
- There should be a new field 387, named REPRESENTATIVE EXPRESSION CHARACTERISTICS
- This field should be repeatable
- Subfields:
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- 2 Source of term (NR)
- 3 Materials specified (NR)
- 6 Linkage (NR)
- 7 Data provenance (R)
- 8 Field link and sequence number (R)
- a Aspect ratio of representative expression (R)
- b Color content of representative expression (R)
- c Content type of representative expression (R)
- d Date of capture of representative expression (R)
- e Date of representative expression (R)
- f Duration of representative expression (R)
- g Intended audience of representative expression (R)
- h Language of representative expression (R)
- i Place of capture of representative expression (R)
- j Projection of cartographic content of representative expression (R)
- k Scale of representative expression (R)
- l Script of representative expression (R)
- m Sound content of representative expression (R)
- There should be one new subfield in field 388
- 7 Data provenance (R)
- There should be one new subfield in field 490
- 7 Data provenance (R)
- There should be one new subfield in field 500
- 7 Data provenance (R)
- There should be one new subfield in field 501
- 7 Data provenance (R)
- There should be one new subfield in field 502
- 7 Data provenance (R)
- There should be one new subfield in field 505
- 7 Data provenance (R)
- Field 507 should now be named SCALE NOTE FOR VISUAL MATERIALS
- There should be one new subfield in field 508
- 7 Data provenance (R)
- There should be one new subfield in field 510
- 7 Data provenance (R)
- There should be one new subfield in field 515
- 7 Data provenance (R)
- There should be one new subfield in field 518
- 7 Data provenance (R)
- There should be one new subfield in field 520
- 7 Data provenance (R)
- There should be one new subfield in field 533
- y Data provenance (R)
- There should be one new subfield in field 546
- 7 Data provenance (R)
- There should be one new subfield in field 550
- 7 Data provenance (R)
- There should be one new subfield in field 555
- 7 Data provenance (R)
- There should be one new subfield in field 583
- 7 Data provenance (R)
- There should be one new subfield in field 600
- 7 Data provenance (R)
- There should be one new subfield in field 610
- 7 Data provenance (R)
- There should be one new subfield in field 611
- 7 Data provenance (R)
- There should be one new subfield in field 630
- 7 Data provenance (R)
- There should be one new subfield in field 648
- 7 Data provenance (R)
- There should be one new subfield in field 650
- 7 Data provenance (R)
- There should be one new subfield in field 651
- 7 Data provenance (R)
- There should be one new subfield in field 653
- 7 Data provenance (R)
- There should be one new subfield in field 655
- 7 Data provenance (R)
- There should be one new subfield in field 700
- 7 Data provenance (R)
- There should be one new subfield in field 710
- 7 Data provenance (R)
- There should be one new subfield in field 711
- 7 Data provenance (R)
- There should be one new subfield in field 751
- 7 Data provenance (R)
- There should be one new subfield in field 760
- l Data provenance (R)
- There should be one new subfield in field 762
- l Data provenance (R)
- There should be one new subfield in field 765
- l Data provenance (R)
- There should be one new subfield in field 767
- l Data provenance (R)
- There should be one new subfield in field 770
- l Data provenance (R)
- There should be one new subfield in field 772
- l Data provenance (R)
- There should be one new subfield in field 773
- l Data provenance (R)
- There should be one new subfield in field 774
- l Data provenance (R)
- There should be one new subfield in field 775
- l Data provenance (R)
- There should be one new subfield in field 776
- l Data provenance (R)
- There should be one new subfield in field 777
- l Data provenance (R)
- There should be one new subfield in field 780
- l Data provenance (R)
- There should be one new subfield in field 785
- l Data provenance (R)
- There should be one new subfield in field 786
- l Data provenance (R)
- There should be one new subfield in field 787
- l Data provenance (R)
- There should be a new field 788, named PARALLEL DESCRIPTION IN ANOTHER LANGUAGE OF CATALOGING
- This field should be repeatable
- Subfields:
- 4 Relationship (R)
- 5 Institution to which field applies (NR)
- 6 Linkage (NR)
- 8 Field link and sequence number (R)
- a Main entry heading (NR)
- b Edition (NR)
- d Place, publisher, and date of publication (NR)
- e Language of cataloging (NR)
- i Relationship information (R)
- l Data provenance (R)
- n Note (R)
- s Uniform title (NR)
- t Title (NR)
- w Record control number (R)
- x International Standard Serial Number (NR)
- There should be one new subfield in field 800
- y Data provenance (R)
- There should be one new subfield in field 810
- y Data provenance (R)
- There should be one new subfield in field 811
- y Data provenance (R)
- There should be one new subfield in field 830
- y Data provenance (R)
- There should be one new subfield in field 856
- e Data provenance (R)
- Subfield l is renamed Standardized information governing access (R)
- Subfield n is renamed Terms governing access (R)
- Subfield r is renamed Standardized information governing use and reproduction (R)
- Subfield t is renamed Terms governing use and reproduction (R)
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
iThis patch updates the default MARC21 framework to reflect the changes brought by Update 33 (November 2021).
To test:
1. Apply patch and restart
2. Go to Administration > MARC bibliographic framework
3. Click Actions next to the default framework and choose MARC structure
4. Check for the changes detailed in the update https://www.loc.gov/marc/up33bibliographic/bdapndxg.html
- There should be a new subfield in field 340
- l Binding (R)
- There should be a new subfield in field 344
- j Original capture and storage technique (R)
- There should be two new subfields in field 490
- y Incorrect ISSN (R)
- z Canceled ISSN (R)
**Note that subfield 7 was added in a later update and is therefore not included in this patch
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Fixes a small typo that prevented the yaml from loading correctly
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch updates the default MARC21 framework to reflect the changes brought by Update 32 (June 2021).
To test:
1. Apply patch and restart
2. Go to Administration > MARC bibliographic framework
3. Click Actions next to the default framework and choose MARC structure
4. Check for the changes detailed in the update https://www.loc.gov/marc/up32bibliographic/bdapndxg.html
- There should be two new subfields in field 022
- 0 Authority record control number or standard number (NR)
- 1 Real World Object URI (R)
- There should be three new subfields in field 046
- 3 Materials specified (NR)
- x Nonpublic note (R) (this one should be hidden from the OPAC)
- z Public note (R)
**Note that subfield 7 was added in a later update and is therefore not included in this patch
- Subfield 082$2 should now be named Edition information
- Subfield 083$2 should now be named Edition information
- There should be a new field 334, named MODE OF ISSUANCE
- This field should be repeatable
- Subfields:
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- 2 Source (NR)
- 6 Linkage (NR)
- 8 Field link and sequence number (R)
- a Mode of issuance term (NR)
- b Mode of issuance code (NR)
- There should be one new subfield in field 344
- i Sound content (R)
**Note that subfield j was added in a later update and is therefore not included in this patch
- Field 348 should now be named NOTATED MUSIC CHARACTERISTICS
- There should be two new subfields
- c Form of musical notation term (R)
- d Form of musical notation code (R)
**Note that subfield 7 was added in a later update and is therefore not included in this patch
- There should be a new field 353, named SUPPLEMENTARY CONTENT CHARACTERISTICS
- This field should be repeatable
- Subfields:
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- 2 Source (NR)
- 3 Materials specified (NR)
- 6 Linkage (NR)
- 8 Field link and sequence number (R)
- a Supplementary content term (NR)
- b Supplementary content code (NR)
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Added missing 881$a subfield.
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch updates the default MARC21 framework to reflect the changes brought by Update 30 (Dec. 2020).
To test:
1. Apply patch and restart
2. Go to Administration > MARC bibliographic framework
3. Click "Actions" next to the default framework and choose "MARC structure"
4. Check for the changes detailed in the update https://www.loc.gov/marc/up31bibliographic/bdapndxg.html
- Field 043 should now be repeatable
- There should be a new field 335, named EXTENSION PLAN
- This field should be repeatable
- Subfields:
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- 2 Source (NR)
- 3 Materials specified (NR)
- 6 Linkage (NR)
- 8 Field link and sequence number (R)
- a Extension plan term (NR)
- b Extension plan code (NR)
**Note that subfield 7 was added in a later update and is therefore not included in this patch
- Field 345 should now be named MOVING IMAGE CHARACTERISTICS
- There should be two new subfields
- c Aspect ratio value (R)
- d Aspect ratio designator (R)
- There should be two new subfields in field 384
- 0 Authority record control number or standard number (R)
- 1 Real World Object URI (R)
- The following subfields of field 856 should have an [OBSOLETE] mention and be hidden (shown in OPAC and intranet, but not editor)
- b Access number [OBSOLETE]
- h Processor of Request [OBSOLETE]
- i Instruction [OBSOLETE]
- j Bits per second [OBSOLETE]
- k Password [OBSOLETE]
- l Logon [OBSOLETE]
- n Name of location of host [OBSOLETE]
- r Settings [OBSOLETE]
- t Terminal emulation [OBSOLETE]
- There should be a new field 881, named MANIFESTATION STATEMENTS
- This field should be repeatable
- Subfields:
- 3 Materials specified (NR)
- 6 Linkage (NR)
- 8 Field link and sequence number (R)
- a Manifestation statement, high-level/general (R)
- b Manifestation identifier statement (R)
- c Manifestation title and responsibility statement (R)
- d Manifestation edition statement (R)
- e Manifestation production statement (R)
- f Manifestation publication statement (R)
- g Manifestation distribution statement (R)
- h Manifestation manufacture statement (R)
- i Manifestation copyright statement (R)
- j Manifestation frequency statement (R)
- k Manifestation designation of sequence statement (R)
- l Manifestation series statement (R)
- m Manifestation dissertation statement (R)
- n Manifestation regional encoding statement (R)
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch makes additional updates to the RELTERMS authorized
value list to make it match the MARC Code List for Relators
at https://www.loc.gov/marc/relators/relaterm.html and
https://www.loc.gov/marc/relators/relacode.html
It also updates the description displayed in the
authorized values list.
Test plan:
1. Apply the patch.
2. Reload the values (reset_all if using KTD).
3. Go to Administration > Authorized values.
4. Note that the description for RELTERMS is changed
(now says 'MARC Code List for Relators
(https://www.loc.gov/marc/relators/).' instead of
'French terms of relations').
5. Check that the changes listed are incorporated
into the RELTERMS authorized values list.
Additions:
prv - Provider
rcd - Recordist
stg - Setting
Changes:
aui - Author of introduction -> Author of introduction, etc.
aus - Author of screenplay -> Screenwriter
coe - Contestant -appellee -> Contestant-appellee
cot - Contestant -appellant -> Contestant-appellant
cou - Court-governed -> Court governed
dpb -> dbp - Distribution place
dgg - Degree grantor -> Degree granting institution
osp - On-screen presenter -> Onscreen presenter
pte - Plaintiff -appellee -> Plaintiff-appellee
rcp - Recipient -> Addressee
red - Redactor -> Redaktor
wde - Wood-engraver -> Wood engraver
Removals:
-grt - Graphic technician
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Update sdg Stage director to sgd (May 31, 2013 technical notice).
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch adds missing relator codes/terms to the marc21_relatorterms.yaml file in accordance with the August 8, 2023 technical notice.
https://www.loc.gov/marc/relators/tn230808rel.html
To test:
1. Apply patch and restart
2. Go to Administration > Authorized values > RELTERMS
--> New terms should be there
anc - Announcer
aue - Audio engineer
aup - Audio producer
bka - Book artist
cad - Casting director
cop - Camera operator
dbd - Dubbing director
djo - DJ
edd - Editorial director
fon - Founder
mka - Makeup artist
mup - Music programmer
mxe - Mixing engineer
nan - News anchor
onp - Onscreen participant
rap - Rapporteur
rxa - Remix artist
sde - Sound engineer
sfx - Special effects provider
swd - Software developer
tau - Television writer
tlg - Television guest
tlh - Television host
vfx - Visual effects provider
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch adds missing relator codes/terms to the marc21_relatorterms.yaml file in accordance with the April 26, 2021 technical notice.
https://www.loc.gov/marc/relators/tn210426rel.html
To test:
1. Apply patch and restart
2. Go to Administration > Authorized values > RELTERMS
--> New term should be there
Addition:
pad - Place of address
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch adds missing relator codes/terms to the marc21_relatorterms.yaml file in accordance with the December 21, 2020 technical notice.
https://www.loc.gov/marc/relators/tn201214src.html
To test:
1. Apply patch and restart
2. Go to Administration > Authorized values > RELTERMS
--> New term should be there
Addition:
dgc - Degree committee member
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch adds missing relator codes/terms to the marc21_relatorterms.yaml file in accordance with the February 21, 2014 technical notice.
https://www.loc.gov/marc/relators/tn140221rel.html
To test:
1. Apply patch and restart
2. Go to Administration > Authorized values > RELTERMS
--> New terms should be there and modified terms should be changed
Additions:
dgs - Degree supervisor
med - Medium
mtk - Minute taker
vac - Voice actor
wst - Writer of supplementary textual content
win - Writer of introduction
wpr - Writer of preface
Changes:
orm - Organizer
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch adds missing relator codes/terms to the marc21_relatorterms.yaml file in accordance with the May 31, 2013 technical notice.
https://www.loc.gov/marc/relators/tn130531rel.html
To test:
1. Apply patch and restart
2. Go to Administration > Authorized values > RELTERMS
--> New terms should be there and deprecated terms should have been removed
Additions:
abr - Abridger
apl - Appellant
ape - Appellee
adi - Art director
ato - Autographer
brl - Braille embosser
brd - Broadcaster
cas - Caster
cor - Collection registrar
cou - Court-governed
crt - Court reporter
edc - Editor of compilation
edm - Editor of moving image work
enj - Enacting jurisdiction
fds - Film distributor
fmk - Filmmaker
fmd - Film director
fmp - Film producer
his - Host institution
isb - Issuing body
jud - Judge
jug - Jurisdiction governed
osp - On-screen presenter
pan - Panelist
pra - Praeses
pre - Presenter
prn - Production company
prs - Production designer
rdd - Radio director
rpc - Radio producer
rsr - Restorationist
sll - Seller
sgd - Stage director
tld - Television director
tlp - Television producer
wac - Writer of added commentary
wat - Writer of added text
wal - Writer of added lyrics
Deprecated relators:
clb - Collaborator
voc - Vocalist
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Must also apply bug 34332 - fixed a syntax error for the pos email template
To test:
1. Configure your Koha to enable the point of sale system (i.e. enable syspref,
set up a register, set up an item to sell).
2. Complete a transaction in the POS system.
3. Click on the “Email receipt” button next to the “Print receipt” option and
enter an email address and confirm that the email is sent.
4. Check the “Tendered” field. It is showing up as 0.00 and not reflecting the
actual amount that was tendered.
5. Apply patch
6. Repeat steps 2 & 3
7. The emailed receipt is now showing the correct tendered amount.
8. Sign off!
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This fixes the typo 'Thankyou' in some of the sample notices.
To test:
* With the sample data
* Create and run a report:
SELECT code,content FROM letter where content LIKE "%Thankyou%";
* Verify 3 notices contain 'Thankyou'
* Apply patch
* Drop your database
* Run the web installer
* Run report again, you should no longer get any results
Signed-off-by: Alexander Wagner <alexander.wagner@desy.de>
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Signed-off-by: Jonathan Field <jonathan.fieeld@ptfs-europe.com>
Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
We shouldn't be including tag 147 in every authority MARC framework we
install, since like all 1xx authority tags there should only be
one per record. It only belongs in a NAME_EVENT framework, which we
don't install.
Test plan:
1. Apply patch, kd && ku or however you like to restart
2. Administration - Authority types - Actions button for Default
- MARC structure
3. In the search box below the text "Select an authority framework"
enter 147 and click OK
4. Once you see that it exists in Default, switch the dropdown to
each of the other frameworks and verify it doesn't appear in
any.
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Both fixes concern the TICKET_NOTIFY message.
* biblio-title.inc builds a link with the intention
of using it inside the Koha GUI. Therefore the baseURL part
is missing. But we can use it for display and wrap it into
a link.
* Changes second link from reading 'page' to 'concern management
page'. Accessiblity guidelines teach us that you should not link
general terms, but always be specific.
To test:
1. Make sure staffClientBaseURL is filled correctly
2. Enable CatalogConcerns
3. Enter an email address in CatalogerEmails
4. Go to a bibliographic record in the staff interface or in the OPAC
5. Click New > New catalog concern
6. Fill out the form and click Submit
7. Check the message_queue table for the message
8. Verify the first link is not working (incomplete) and the second is 'page'
9. Apply patch, drop db, create db and run web installer
10. Repeat setup and testing
11. Both links should now be updated and working
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This fixes the system preference name from IntranetBaseURL to
staffClientBaseURL.
As this feature has just been pushed I chose to fix the
database updates that will be run when installing 23.05.
To test:
* Verify the wrong link in TICKET_NOTIFY
* Drop database, create database, run web installer
* Verify the link is now correct in the notice
Bonus: Test update from 22.11 to 23.05 and verify the
notices are correct there as well.
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Signed-off-by: Owen Leonard <oleonard@myacpl.org>
Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
This patch moves account debit and credit types, as well as the CASH
payment type, into YAML files under
installer/data/en/mandatory. This should make the debit and credit types
translatable (for new installations only).
To test:
1. Apply patch
2. Update po files
./misc/translator/translate update xx-XX
3. View the xx-XX-installer.po file
-->The default account debit and credit types (and cash payment type)
should be available to be translated
4. Translate the strings
5. Apply the translations
./misc/translator/translate install xx-XX
6. Load the new translated YAML files (with a fresh install, or by deleting
the values in the db and using ./misc/load_yaml.pl to load the files)
7. In the staff interface, go to Administration > Credit types
--> They should be translated
8. Go to Administration > Debit types
--> They should be translated
Signed-off-by: Magnus Enger <magnus@libriotech.no>
Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
We've identified 3 issues:
* Name of patron is not showing up in subject line
* Name of patron is now showing in notice text
* Notice is set to be HTML, but has no line breaks and uses no HTML tags
In the database update, these issues don't occur:
$dbh->do( q{
INSERT IGNORE INTO letter (module, code, name, title, content, message_transport_type) VALUES ('members', 'PASSWORD_CHANGE', 'Notification of password change', 'Library account password change notification',
"Dear [% borrower.firstname %] [% borrower.surname %],\r\n\r\nWe want to notify you that your password has been changed. If you did not change it yourself (or requested that change), please contact library staff.\r\n\r\nYour library.", 'email');
});
So this patch will make them match up:
* Remove HTML flag
* Update patron. to borrower. in message text
* Remove patron name from subject (it won't work even with the correct variables)
To test:
* Add an email address to your favourite sample user
* Make sure NotifyPasswordChange is set to "Notify"
* Update the sample user's password using the "change password" feature
* Verify a notice is shown in the notices tabs
Note: you won't see the line break issue there because of bug 30287
* Apply patch
* Recreate your database/run web installer so sample notices are loaded
* Repeat the test, it should generate a nice lookig notice now
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
