Summary: | Info around CSV export profiles edition not correct for sql option | ||
---|---|---|---|
Product: | Koha | Reporter: | Thibaud Guillot (thibaud_g) <thibaud.guillot> |
Component: | Serials | Assignee: | 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
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... 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. |