Bug 38824 - Document the use of type field in packages (ERM)
Summary: Document the use of type field in packages (ERM)
Status: Needs documenting
Alias: None
Product: Koha
Classification: Unclassified
Component: Documentation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-04 17:17 UTC by Mathieu Saby
Modified: 2025-01-04 17:17 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 Mathieu Saby 2025-01-04 17:17:28 UTC
The use of "type" field is not explained. What are the meaning of the standard default values, and the recommended use of this field?

The standard default value in ERM_PACKAGE_TYPE AV are "complete" and "local"

In EBSCO knowlegde base, the values are "complete", "variable", "selectable" and "custom", with meanings explained here : https://connect.ebsco.com/s/article/What-are-the-available-Package-Types-in-Holdings-Management?language=en_US

If EBSCO eHoldings are used in Koha (with HoldingsIQ API), I suppose those values are going to be used ? So maybe the standard values in ERM_PACKAGE_TYPE should be updated to reflect that ?

But is this field of any use if you do not use EBSCO eHoldings? Do you need to select the value "local" ?