Bug 37015 - Expose external_id in the ERM packages form and views
Summary: Expose external_id in the ERM packages form and views
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: ERM (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Jonathan Druart
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-03 10:57 UTC by Katrin Fischer
Modified: 2024-10-01 13:02 UTC (History)
7 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2024-06-03 10:57:05 UTC
While the ERM module was in development we had made a case for an external ID field for packages. This was added to the database, but the field cannot be added, edited or viewed from the GUI. 

We would like to use this to store the national identifiers for packages. They would then be used to match bibliographic records to their packages.
Comment 1 Katrin Fischer 2024-06-30 21:14:01 UTC
Hm, it looks like it has been hidden for some reason?

                    <li v-if="false">
                        <label>{{ $__("External ID") }}:</label>
                        <span>
                            <span v-if="false"
                                >FIXME - Does not replace this v-if with an HTML
                                comment, it breaks xgettext</span
                            >
                            <span v-if="false"
                                >FIXME - Create a syspref to store the URL</span
                            >
                            <a
                                :href="`https://replace_with_syspref_value_here.folio.ebsco.com/eholdings/packages/${erm_package.vendor.external_id}-${erm_package.external_id}`"
                            >
                                {{ erm_package.vendor.external_id }}-{{
                                    erm_package.external_id
                                }}
                            </a>
                        </span>
                    </li>
Comment 2 Jonathan Druart 2024-09-24 10:27:54 UTC
(In reply to Katrin Fischer from comment #1)
> Hm, it looks like it has been hidden for some reason?

"FIXME - Create a syspref to store the URL"
Comment 3 Katrin Fischer 2024-09-25 15:28:31 UTC
(In reply to Jonathan Druart from comment #2)
> (In reply to Katrin Fischer from comment #1)
> > Hm, it looks like it has been hidden for some reason?
> 
> "FIXME - Create a syspref to store the URL"

I saw the comment, but I didn't understand the meaning. For our use case the ID would not be an URL, but an alphanumeric ID.
Comment 4 Jonathan Druart 2024-09-26 11:29:15 UTC
(In reply to Katrin Fischer from comment #3)
> (In reply to Jonathan Druart from comment #2)
> > (In reply to Katrin Fischer from comment #1)
> > > Hm, it looks like it has been hidden for some reason?
> > 
> > "FIXME - Create a syspref to store the URL"
> 
> I saw the comment, but I didn't understand the meaning. For our use case the
> ID would not be an URL, but an alphanumeric ID.

It has been hidden because we cannot link to FOLIO. You were asking the reason, I just told you why it is not displayed.

external_id is not an URL currently, I am talking about this URL:
50                                 :href="`https://replace_with_syspref_value_here.folio.ebsco.com/eholdings/packages/${erm_package.vendor.external_id}-${erm_package.external_id}`"

If you have a reason to display it, feel free to do it.
Comment 5 Katrin Fischer 2024-10-01 12:16:01 UTC
Maybe we could talk about this next week. We are investigating ways to link to another knowledge base, not FOLIO. In our case the external_id would be a national identifier for the package on this level which presents as a somewhat short alpha-numeric code. We would want libraries to be able to add their own packages, including entering the identifier that would later be used to match bibliographic records to the packages/titles/resources.
Comment 6 Pedro Amorim 2024-10-01 13:02:52 UTC
Hi guys, adding my 2 cents here, ignore if not applicable.
As I understand it, external_id in erm_eholdings_packages is used for the linkage with EBSCO HoldingsIQ, and was/is designed to be governed by Koha's ERM, not the end user.

(In reply to Katrin Fischer from comment #5)
> Maybe we could talk about this next week. We are investigating ways to link
> to another knowledge base, not FOLIO. In our case the external_id would be a
> national identifier for the package on this level which presents as a
> somewhat short alpha-numeric code. We would want libraries to be able to add
> their own packages, including entering the identifier that would later be
> used to match bibliographic records to the packages/titles/resources.

We are adding additional fields support for ERM packages in bug 37577. Surely it would satisfy your use case Katrin? You can configure a Folio ID field, a national identifier or anything else.