Bug 34442

Summary: Info around CSV export profiles edition not correct for sql option
Product: Koha Reporter: Thibaud Guillot (thibaud_g) <thibaud.guillot>
Component: SerialsAssignee: Thibaud Guillot (thibaud_g) <thibaud.guillot>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: trivial    
Priority: P5 - low CC: r.delahunty
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Thibaud Guillot (thibaud_g) 2023-07-28 13:16:26 UTC
Hello everyone,

When you edit a CSV export profile, we can have a few examples to see how it works, such as. 
"For late issue claims, you can use data from the following tables: serial, subscription, biblio, biblioitems and aqbookseller".

But there's an error here, if I want to add subscription.callnumber for example (or id etc...) it doesn't work... Perhaps we can correct this description a little? But how? Just to say that there are only these fields you can include:

[SQL query extracted from the GetLateOrMissingIssues function]
"serialid, aqbooksellerid, name,
 biblio.title, biblioitems.issn, planneddate, serialseq,
 serial.status, serial.subscriptionid, claimdate, claims_count,
 subscription.branchcode, serial.publisheddate"

This may be a bit longer, but I'd rather ask the community what's the best way to be clear on this point.
Thanks for your feedback
Comment 1 Thibaud Guillot (thibaud_g) 2023-07-28 13:18:04 UTC
I can be more precise, i.e. if some users want to have such and such a field, this will create as many BZs in the future...
Comment 2 Ray Delahunty 2023-08-10 11:41:49 UTC
Let me be the first person to add here that we really do need more fields able to be added to the late issue claims csv export. (Actually Thibaud, in 22.11 and 21.11 we are able to add subscription.branchcode). But **at least**, we would want subtitle, and we are considering using callnumber to house the vendor's own vendor number, as the note and the internalnote fields are already used locally. (And we can't even add the subscription.note field to the csv export). Or if we created a 'vendornum' field in the additional_fields table, it would be great to be able to pull the vendornum data from there into the csv file for shipping to the vendor.