Summary: | ILL: Allow to configure displayed data for staff interface and OPAC separately | ||
---|---|---|---|
Product: | Koha | Reporter: | Magnus Enger <magnus> |
Component: | ILL | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | martin.renvoize, Niamh.WalkerHeadon |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Magnus Enger
2019-02-07 09:23:18 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. (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. (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. |