Bug 38911

Summary: Map optional KBART columns to additional fields in ERM titles
Product: Koha Reporter: Mathieu Saby <mathsabypro>
Component: ERMAssignee: Jonathan Druart <jonathan.druart>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: jonathan.druart, jonathan.field, martin.renvoize, matt.blenkinsop, michaela.sieber, pedro.amorim
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:
Bug Depends on: 40192    
Bug Blocks:    

Description Mathieu Saby 2025-01-16 16:49:53 UTC
If the KBART file imported contains an optional column not defined by the format (like "bestpnn" column present in KBART files imported from https://bacon.abes.fr/ ), this information is lost by Koha, while it may be useful.

We could store it in that way : 
- give the ability to create additional custom fields for ERM titles (like agreements or packages)
- give the ability to map an optional KBART column with the custom field
Comment 1 Katrin Fischer 2025-01-17 10:12:48 UTC
I like the idea of using additional fields for this with a mapping on the name of the column. GOKb also uses additional fields in their KBART exports and storing that information could be very useful.