Bug 38796 - ERM : record for print documents should not be imported into ERM
Summary: ERM : record for print documents should not be imported into ERM
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: ERM (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Jonathan Druart
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-29 17:23 UTC by Mathieu Saby
Modified: 2025-01-04 10:31 UTC (History)
5 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 Mathieu Saby 2024-12-29 17:23:49 UTC
Not sure if it is a bug or not, but I don't understand the purpose of importing records of "print" documents (without a link in 856) into ERM
Currently Koha imports them but the field "coverage_depth" takes the value "print"

Is it useful for some workflows ?
Perhaps those records should better not be taken into account if they are present in the list ?
Comment 1 Jonathan Field 2024-12-30 09:57:13 UTC
(In reply to Mathieu Saby from comment #0)
> Not sure if it is a bug or not, but I don't understand the purpose of
> importing records of "print" documents (without a link in 856) into ERM
> Currently Koha imports them but the field "coverage_depth" takes the value
> "print"
> 
> Is it useful for some workflows ?
> Perhaps those records should better not be taken into account if they are
> present in the list ?

Hi, Can you explain this a bit further? Do you mean you don't understand why we create MARC catalogue records for KBART items? In 24.11 it is now optional whether you create bib records or not (it's a checkbox). If you choose "Y" there is limited logic behind what is created but some libraries like to store a basic catalogue record of databases, ebooks etc. they hold in the catalogue. Have I understood that correctly?
Comment 2 Mathieu Saby 2025-01-04 10:31:52 UTC
My ticket may have been premature, I'm testing the whole ERM module to present it to colleagues, but I don't yet have the full picture. We'll comment again if necessary...