Bug 22285 - ILL: Allow to configure displayed data for staff interface and OPAC separately
Summary: ILL: Allow to configure displayed data for staff interface and OPAC separately
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: ILL (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-07 09:23 UTC by Magnus Enger
Modified: 2023-06-06 07:13 UTC (History)
2 users (show)

See Also:
GIT URL:
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 Magnus Enger 2019-02-07 09:23:18 UTC
When ILL is enabled, patrons get an extra "tab" in "my summary" in the OPAC, called "your interlibrary loan requests". This page shows a table of basic info about ILL requests for that patron, along with a button that says "View". Clicking on this button shows a lot of information about a single request. 

The first part of the page has a heading of "Details from library" and contains the same fields as the table on the previous page, along with a field for notes. (It looks like this field can be edited both by the patron and by librarians, which seems kind of odd, but that is better left for another bug.)

The second part is labeled "Details from <supplier/backend>", and this is the problematic bit. It is identical to the information displayed to librarians in the backend, so it might contain notes that are not meant for the patron to see. 

The data in this section comes from Koha::Illbackends::Libris::Base:metadata(). Could it be possible to give this sub a parameter so that it would "know" if it is serving data for the OPAC or the intranet, and choose which data to display based on that?
Comment 1 Katrin Fischer 2023-01-13 11:02:47 UTC
Hi Magnus, could you give an example for problematic info displayed?

For the notes we have a staff and an OPAC note, I think only the OPAC note displays in the OPAC.

For the provider display I only see a few fields actually of our metadata. I wonder how they are selected and how we could improve on it.
Comment 2 Magnus Enger 2023-01-17 07:14:06 UTC
(In reply to Katrin Fischer from comment #1)
> Hi Magnus, could you give an example for problematic info displayed?

I think it depends on the backend. 

> For the notes we have a staff and an OPAC note, I think only the OPAC note
> displays in the OPAC.

In Libris you can also have a note that is written when you add enter the request into Libris, and this is imported to Koha along with all the other metadata. 

> For the provider display I only see a few fields actually of our metadata. I
> wonder how they are selected and how we could improve on it.

I think every backend must have a metadata() sub, that returns some metadata about a given request. And I think what I found problematic is that this is used both for the OPAC and the Intranet, so you either have to display too little information to librarians or too much information to patrons. It would be better to have e.g. metadata_public() or metadata({ public => 1 }) for use in the OPAC, or something like that.
Comment 3 Katrin Fischer 2023-01-17 12:27:46 UTC
(In reply to Magnus Enger from comment #2)
> (In reply to Katrin Fischer from comment #1)
> > Hi Magnus, could you give an example for problematic info displayed?
> 
> I think it depends on the backend. 
> 
> > For the notes we have a staff and an OPAC note, I think only the OPAC note
> > displays in the OPAC.
> 
> In Libris you can also have a note that is written when you add enter the
> request into Libris, and this is imported to Koha along with all the other
> metadata. 
> 
> > For the provider display I only see a few fields actually of our metadata. I
> > wonder how they are selected and how we could improve on it.
> 
> I think every backend must have a metadata() sub, that returns some metadata
> about a given request. And I think what I found problematic is that this is
> used both for the OPAC and the Intranet, so you either have to display too
> little information to librarians or too much information to patrons. It
> would be better to have e.g. metadata_public() or metadata({ public => 1 })
> for use in the OPAC, or something like that.

Ok, that makes a lot of sense. We also have some internal attributes, but they display neither in OPAC nor staff... now I guess I know why! Updating the description.