Bug 20153

Summary: Add new column "source" in the authorities pages's result
Product: Koha Reporter: Patrick Robitaille <patrick.robitaille>
Component: CatalogingAssignee: Olli-Antti Kivilahti <olli-antti.kivilahti>
Status: Needs Signoff --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: koha, lari.taskula, laurence.rault, m.de.rooy, marjorie.barry-vila, olli-antti.kivilahti, phil
Version: unspecified   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: Bug 20153: Add new column "source" in the authorities pages's result
Bug 20153: (follow-up) Add origincode support for Zebra
Bug 20153: (QA follow-up) Fix tidiness
Bug 20153: Add new column "source" in the authorities pages's result
Bug 20153: (follow-up) Add origincode support for Zebra
Bug 20153: (QA follow-up) Fix tidiness

Description Patrick Robitaille 2018-02-07 15:57:09 UTC
hi, 

It would be nice if we could add a new column in the results page of a search in authority's module.In this new column we could se the subfield 040 $a who show the Organization that performed the original cataloging. With this new column  with this new column titled "source", like the column in the z39.50 search, we would not need to go back to the authority record to see if it's a locally created authority or if it's imported.

Patrick.
Comment 1 Koha collecto 2024-05-10 18:53:11 UTC
+1
Comment 2 Olli-Antti Kivilahti 2024-09-16 13:39:03 UTC
+1
Comment 3 Olli-Antti Kivilahti 2024-09-16 16:34:07 UTC
Created attachment 171569 [details] [review]
Bug 20153: Add new column "source" in the authorities pages's result

Populates the already existing
  auth_header.origincode
from MARC Authorities CRUD.

Displays it in the authorities search results from the cataloguing tool and
from the authorities search module.

MARC21 cataloguing rules are followed to populate it automatically, but I have
no knowledge of UNIMARC/etc to implement origincode autovifivication for those.

TEST PLAN (MARC21)
1. Create a MARC Authorities Record
2. Optionally define MARC Framework for Authority auth_header.origincode
3. Populate 040$ca or 024$2 or 003 or the subfield at
   MARC Framework for Authority auth_header.origincode
4. Search for the Auth Record
5. Observe a new 'Origin'-tab in the search results has the defined 'Cataloguing Source'.
5a. Page: authorities/auth_finder.pl
5b. Page: authorities/authorities-home.pl

TEST PLAN (Others)
0. Same as MARC21, but the MARC FW for Auth is mandatory.
Comment 4 Laurence Rault 2024-09-26 19:25:33 UTC
Tested on sandbox : 

TEST PLAN (MARC21)
1. Create a MARC Authorities Record
=> ok
2. Optionally define MARC Framework for Authority auth_header.origincode
=> KO
kohafield is not populated in auth_subfield_structure

3. Populate 040$ca or 024$2 or 003 or the subfield at
   MARC Framework for Authority auth_header.origincode
=> OK
=> auth_header.origincode is populated with the field content (040$a)
4. Search for the Auth Record
=> OK
5. Observe a new 'Origin'-tab in the search results has the defined 'Cataloguing Source'.
5a. Page: authorities/auth_finder.pl
5b. Page: authorities/authorities-home.pl
=> KO
No Origin tab
There is a column Source column which is empty
Comment 5 Lari Taskula 2025-10-21 09:42:08 UTC
Created attachment 188205 [details] [review]
Bug 20153: (follow-up) Add origincode support for Zebra
Comment 6 Lari Taskula 2025-10-21 09:42:10 UTC
Created attachment 188206 [details] [review]
Bug 20153: (QA follow-up) Fix tidiness
Comment 7 Lari Taskula 2025-10-21 09:51:04 UTC
(In reply to Laurence Rault from comment #4)
> 5. Observe a new 'Origin'-tab in the search results has the defined
> 'Cataloguing Source'.
> 5a. Page: authorities/auth_finder.pl
> 5b. Page: authorities/authorities-home.pl
> => KO
> No Origin tab
> There is a column Source column which is empty

I think by "tab" they meant "column", as you've noticed.

I noticed the patch added support for Elasticsearch, but not Zebra. I've added a follow-up patch that contains Zebra support. Is it possible your sandbox was using Zebra and due to the lack of Zebra support the column was empty?
Comment 8 Lari Taskula 2025-10-21 10:13:54 UTC
Created attachment 188208 [details] [review]
Bug 20153: Add new column "source" in the authorities pages's result

Populates the already existing
  auth_header.origincode
from MARC Authorities CRUD.

Displays it in the authorities search results from the cataloguing tool and
from the authorities search module.

MARC21 cataloguing rules are followed to populate it automatically, but I have
no knowledge of UNIMARC/etc to implement origincode autovifivication for those.

TEST PLAN (MARC21)
1. Create a MARC Authorities Record
2. Optionally define MARC Framework for Authority auth_header.origincode
3. Populate 040$ca or 024$2 or 003 or the subfield at
   MARC Framework for Authority auth_header.origincode
4. Search for the Auth Record
5. Observe a new 'Source'-column in the search results has the defined 'Cataloguing Source'.
5a. Page: authorities/auth_finder.pl
5b. Page: authorities/authorities-home.pl

TEST PLAN (Others)
0. Same as MARC21, but the MARC FW for Auth is mandatory.
Comment 9 Lari Taskula 2025-10-21 10:13:57 UTC
Created attachment 188209 [details] [review]
Bug 20153: (follow-up) Add origincode support for Zebra
Comment 10 Lari Taskula 2025-10-21 10:13:59 UTC
Created attachment 188210 [details] [review]
Bug 20153: (QA follow-up) Fix tidiness
Comment 11 Lari Taskula 2025-10-21 10:14:26 UTC
Also, I've rebased the first patch.
Comment 12 Chris Cormack 2025-11-21 00:33:01 UTC
Automatic patch test results:

â ï¸ The patch applies with fuzzy option (ignoring whitespace).
This may indicate minor conflicts that need to be resolved.

Details: Patch applies with fuzzy option (ignoring whitespace)

This is an automated message from the patch testing system.