Vendor Record Discussions | Acquisitions Small Group | - Ann-Marie Breaux (Deactivated) reported on vendor record small group. They have met a lot this week, looking at order records. Stacks is working on vendor record screen.
- Vendor Records: Dennis Bridges provided overview of work so far. Lots of contents from Discuss site was incorporated into the page. Shows aliases for vendors now ("AKA" field), plus vendor description. Additional vendor-level contact information being added, including i18n work, person contacts, etc.
- "Activity log" has been discussed; a "change log" exists, and may serve this purpose, but it is being reviewed and discussed.
- Currency selection may be moved as a result of discussion.
- No questions or concerns raised from the group on this topic.
- "Agreements" - a place for recording some information about licensing, with ability to link to external storage of original documents. Could include default discount record, which would be overwritten on specific items in those records. Decided to not try and track everything you'd find in an ERM, in the v1 product.
- Kristin Martin discussed connecting to CORAL as one option to implementing an ERM into FOLIO at the start.
- Question about workflows - how might that work within this layout? Would claiming vary from vendor to vendor - so different workflow structures for different vendors or different types of orders (ie, rush, standing orders, etc.)? Or no claiming in some situations (ebooks)? Note: no EDI-claiming or claim responses within v1; even manual claiming may not be included in v1.
- Many fields in this area serve as defaults, which would be overwritten by information from order records. It will serve as the baseline for order data.
- Tax field: Big deal, particularly for Europeans. Martina Tumulla reported that there are different tax levels for print vs e-resources. They have a new tax (Withholding tax?) for which they will need more information in the database; at least more than 1 set of field for tax. Perhaps add a link field to make it possible to access and review when needed. Need to add note field to tax area, and probably to every area.
- EDI: talked about basics, but there is more to do here. EDI transactions will be orders and invoices only, in Edifact format, for v1. All other sorts of messages, and in other formats, will follow in future versions. EDI code limits are pretty open, as some are using standards like SAN or EAN, while others are using proprietary, or even just mutually-agreed-upon terms. Ann-Marie Breaux (Deactivated) reviewed each of the other fields, check-boxes, etc.
- FTP: storage of FTP details, including notes and "Test Connection" button to confirm that stored login data is accurate.
|