Kohacon19/Workshops/Acquisitions

== Abstract ==
All things acquisitions! We want a varied audience who are keen to get involved in driving the acquisitions module forward. We'd like to hear about your best practices as well as sharing our own experiences. What is your workflow, how could Koha be improved to better support it? One of the key areas we want to focus on for the next release cycle is acquisitions, so now is a great time to jump aboard and share your visions!
== Topics and Ideas Covered ==
* EDI
 - Used extensively in UK
 - Used extensively in USA - Almost every vendor needs their own plugin to work with their 'version' of EDI, little customisation per partner, however.
 - EDItX is used in Finland
 - Populating the local call number and other local information (basket name, basket number, ...) (this is not in th EDI standard and is therefore hard to achieve)
 - Some vendors will work with other LMS/ILS fine but put blame on Koha when they won't configure EDI with a library
 - Can we somehow automatically match suggestions and orders when QUOTE is used
 - We would like a quick workflow for getting purchase suggestions into EDI
 - Vendors are developing new/different APIs which we will soon need to add more support for (GOBI for example)
* General
 - Additional auditing capabilities (logging changes especially budgets and funds) Bug 13325
 - We would like to be able to batch receive all order lines from a basket
 - We would like to be able to customise the fields available/required by suggestions
 - We would like some internal note fields for suggestions that are is visible throughout the acq workflows
 - We would like an invoice note field
 - When orders are staged with a certain framework, that framework is then lost (reset to default) at a later stage ?!
 - Allow archiving of old order and old baskets
 - 
* Email Orders
 - If there are multiple ISBNs in a record, only the first will be emailed to the vendor.. we should be able to choose which one is used
* Permissions - More granular
 - Reopen invoice, edit invoice, reopen basket, edit basket etc.
 - If someone has only suggestions permissions, don't show acquisitions module, maybe show 'suggestions button' instead
* Suggestions
 - Link suggestions to existing records
 - Show biblio information for deleted and cancelled orders
 - Allow turning a suggestion into an ILL request
 - Allow turning an ILL request into a purchase suggestion
* Possible workaround and workflows
 - Blanket POS, written by Round Rock PL - https://docs.google.com/document/d/1SZJsKLddgfA8v7kWcRzf9J0watTKd7HQ__dcwbwmIPk/edit?usp=sharing
== Next acions ==
* Acquisitions user group meetings
* Regular meetings
* Creating a listserv for acquisitions - Ask biblibre to host this
* Acquisitions bug watch, curated list coming out once a month
* Post information on how to join the user group
* Wiki
 - Document what vendors work with EDI and experiences with those vendors.
== Missing features list ==
* Ability to manually set or change the delivery date (currently precalculated) Bug 15348
 * This would become a higher priority as we implement automated claims via EDI
* Ability to create orders without a linked record (binding materials, etc.)
* Ability to receive items without having to create an order first (donations, etc.)
* Ability to add invoice data without having to receive the items first (unlink invoice and receive steps)
* Ability to split price for an order line over mulitple funds (expensive items paid for by multiple faculties)
* Improved email order process
 - Logging for emails sent
 - BCC acq address for all order emails
 - Configuration of From, Reply-To and Return-Patch addresses
 - Template Toolkit Syntax (if not available yet)
* Allow additional costs to be added on order line level at time of order (shipping, packaging) (required for below?)
* Multiple tax types per order line (would require to be able to split the total into multiple partial costs that tax rates are applied to, example: electronic and print have different tax rates, multi-media can be affected)
* Automated claim process (define at vendor or basket level what to auto-claim?)
* Ability to enter the total on the invoice and check against that amount on finishing the receiving process
== Current development projects and bugs ==
* Rounding issues
* Calculation using the tax included/excluded settings on vendor level - how is it expected to work? FIXME bug number
* Advanced Invoicing RFC - https://wiki.koha-community.org/wiki/Advanced_Invoicing_RFC