Skip to end of metadata
Go to start of metadata
Attendees
Discussion items
| Minute taker | |
|
| | - RM SIG meeting cancelled for the 26th.
- TF looking at the roadmap
- how to best use the roadmap and to integrate with SIG work?
- We want to have better context for our work, status of proposals, status, progress, etc
- for the new governance model
- there are currently nominations for community council
- institutions can nominate 1 individual to run (includes a paragraph for justification for that nomination)
- Discuss at the institutional level
|
Vendor Ref number updates (repeating and new types) | Ann-Marie Breaux (Deactivated) | Vendor red number updates: - can add multiple vendor ref number to orders
- and along with a vendor reference type
- new language for types:
 - What is the difference between ongoing and continuations?
- each library can use whatever it wants (not enforced), but the language has been standardized
- the invoice view shows these added vendor ref numbers
- do need to match invoices to POLs (common usage)
- For EDIFACT, the vendor reference comes in, and this process allows for that vendor ref Number to be related to the vendor invoice line
- this increases the options available to match these things that will need to have relationships
- searchable in orders
- from chat (Matching on the SNA was the way OLE edifact invoicing was implemented. It isn’t a required way to match. )
- from chat (While our subscription agents have our POs at the moment, they will need to be updated to include the -1 (we will be a one-line po library))
- trying to finish of the matching of the logic of invoice lines to order lines
- looking for matching in searching
- can grab info from one place and copy it to the other
- suggestion to export POs to have vendor update Order#s
- Folks want to know how proposals, JIRA,s SIG work, etc, fits into the dev timeline, which release, etc
- This feature does not have a ranking attached to it (curious about process and priorities attached to rankings)
- look at info for UXPROD2622
- Very much want to understand how the loops are closed, and developed, etc
- tied to the roadmap theme, goals, plans, efforts from the SIGs, etc
- how to get on the same page
- Developing themes for development
|
- OCLC Single Record Import Functionality
| | - super cool happenings
- if ONLY one record for placing an order against it
- new service as of IRIS that will allow user to stay in Invoices, use a Z39.50 target, and bring in a single record
- settings that control this are maintained in Inventory integrations (Single Record Import)
- can use Library of Congress of OCLC to grab a record
- there is also an ID for the external identifier type (say, LCCN or OCLC)
- best practice use a specific target defined by the ID type (but there are an array of possibilities)
 - when enabled, you will need a OCLC # to grab the record (this is a pull from OCLC, not a push from OCLC)
- the wicked cool part is that one can pick OCLC from the import dropdown to bring in the record
- from chat (Can you search with ISBN? )
- the status of the order produced a holdings and an item
- also, set some of the marc field protections, configured in settings
- The step to overlay can bring in a new version of the record, or can bring in an all different record to overlay that record
- this step will focus the overlay on the current record that is open
- from chat (Will we be able to specify additional import profiles for the process? I'm thinking if we have a standard practice with deleting or adding certain fields would be able to do it on import rather quickmarc post-import )
- would not include local data because it is pulling the master record (for this single import)
- will be coming as part of IRIS
|
Action items
LikeBe the first to like this