Bug 34667 - Update MARC21 default framework to Update 36 (June 2023)
Summary: Update MARC21 default framework to Update 36 (June 2023)
Status: RESOLVED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Bibliographic data support (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Caroline Cyr La Rose
QA Contact: Katrin Fischer
URL:
Keywords:
Depends on: 34665
Blocks:
  Show dependency treegraph
 
Reported: 2023-08-30 19:19 UTC by Caroline Cyr La Rose
Modified: 2023-11-27 18:33 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: Small patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
This enhancement updates the default MARC21 bibliographic framework to reflect changes brought to the format by Update 36 (June 2023). Note that this only affects new installations. For existing installations, you can modify your MARC frameworks in Administration > MARC bibliographic framework. Details of Update 36 are on the Library of Congress Website: https://www.loc.gov/marc/bibliographic/bdapndxg.html
Version(s) released in:
23.11.00


Attachments
Bug 34667: Update MARC21 default framework to Update 36 (June 2023) (29.65 KB, patch)
2023-08-30 20:50 UTC, Caroline Cyr La Rose
Details | Diff | Splinter Review
Bug 34667: Update MARC21 default framework to Update 36 (June 2023) (29.69 KB, patch)
2023-09-02 19:42 UTC, David Nind
Details | Diff | Splinter Review
Bug 34667: Update MARC21 default framework to Update 36 (June 2023) (29.75 KB, patch)
2023-10-06 13:59 UTC, Katrin Fischer
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2023-08-30 19:19:22 UTC
https://www.loc.gov/marc/bibliographic/bdapndxg.html

■ New content designators:
Fields
361Structured Ownership and Custodial History (R)
857Electronic Archive Location and Access (R)
Subfields
$0 Authority record control number or standard number (R) in 653 (Index Term -
           Uncontrolled)
$0 Authority record control number or standard number (R) in 658 (Index Term -
           Curriculum Objective)
$0 Authority record control number or standard number (R) in 720 (Added Entry -
           Uncontrolled Name)
$1 Real World Object URI (R) in 653 (Index Term - Uncontrolled)
$1 Real World Object URI (R) in 658 (Index Term - Curriculum Objective)
$1 Real World Object URI (R) in 720 (Added Entry - Uncontrolled Name)
$3 Materials specified (NR) in 041 (Language Code)
$5 Institution to which field applies (NR) in 653 (Index Term - Uncontrolled)
$5 Institution to which field applies (NR) in 720 (Added Entry - Uncontrolled Name)
$7 Data provenance (R) in 720 (Added Entry - Uncontrolled Name)

■ Editorial modifications:
Most of the following fields/appendix do not have technical changes but contain editorial modifications (in red). A full description of editorial changes for each entry can be found in the linked MARC Proposal referenced.

Fields
008/35-37All Materials (NR) from Proposal 2023-02
041           Language Code from Proposal 2023-02
561          Ownership and Custodial History from Proposal 2023-04
Appendix
Appendix JData Provenance Subfields from Proposal 2023-01
Comment 1 Caroline Cyr La Rose 2023-08-30 20:50:54 UTC Comment hidden (obsolete)
Comment 2 David Nind 2023-09-02 19:42:35 UTC
Created attachment 155175 [details] [review]
Bug 34667: Update MARC21 default framework to Update 36 (June 2023)

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>
Comment 3 David Nind 2023-09-02 19:47:08 UTC
Testing notes (using KTD):

1. After applying the patch in the ktd shell, I used a reset_all - this refreshes the instance without having to shut down KTD (and incorporates any yml file changes).

2. I amended the patch description - updated URL for update 36.
Comment 4 Katrin Fischer 2023-10-06 13:59:37 UTC
Created attachment 156621 [details] [review]
Bug 34667: Update MARC21 default framework to Update 36 (June 2023)

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>
Comment 5 Tomás Cohen Arazi 2023-10-09 14:43:55 UTC
Pushed to master for 23.11.

Nice work everyone, thanks!
Comment 6 Fridolin Somers 2023-10-09 19:50:08 UTC
Enhancement not pushed to 23.05.x
Comment 7 Aude Charillon 2023-11-27 15:11:31 UTC
Checked Koha Manual - no update needed.
Comment 8 Lauren Denny 2023-11-27 18:20:42 UTC
Will this enhancement be backported to the LTS version, 22.11?  I'm trying to understand how the LTS versions are different than regular upgrade versions.
Comment 9 Katrin Fischer 2023-11-27 18:33:21 UTC
(In reply to Lauren Denny from comment #8)
> Will this enhancement be backported to the LTS version, 22.11?  I'm trying
> to understand how the LTS versions are different than regular upgrade
> versions.

They are not really different when it's about the backporting strategy, but they are maintained longer than regular releases. Please beware: this change here only applies for new installations. As we don't want to touch any custom frameworks with the updates. If you already have a Koha installation, you'll want to add those fields manually if required.