Skip to end of metadata
Go to start of metadata

Date

Attendees


Discussion items

ItemWhoNotes
Minute taker
Announcements/updates

Next week is last week that US is on Standard Time, so be on the lookout for changes to when upcoming meetings will take place.

  • US will change to Daylight Savings Time on March 10, effective as of the March 15 meeting.
  • Europe will change on March 31, effective as of the April 5 meeting (so we'll all be back on the same schedule at this point).
  • After Brexit, we anticipate that the UK will start using a totally new time-keeping system based on 47-second minutes, so it'll be up to them to figure out what time, in NewUK time, meetings will start. (just kidding, obvs)

Product Council review: Kristin Martin, Dracine Hodges, and Holly Mistlebauer are working on an updated gap analysis, especially with focus on institutional requirements, and which features need to be documented for updated Gap Analysis. About 9 months since last analysis, and items now have a lot more stories, etc., to provide more information about them. A feature prioiritzation and gap analysis spreadsheet should be out in a week or two to complete.

Next FOLIO meeting will not happen in May. It may happen in June, most likely around June 17-19; probably in Washington DC or area, before ALA. If you're planning on going to ALA, don't book a ticket yet, because you might want to go early, for FOLIO!

Several folks are going to ER&L conference next week; there is a slack channel about this - if you want to join the Slack channel, contact Kristin Martin to get added. Maybe a breakfast together, or something like that.

Acquisitions:

  • Receiving: mock-up review and status discussion
  • Update to order/inventory interaction

Dennis is present; Ann-Marie is not. We'll review receiving that wasn't covered in last meeting, plus updates on order action.

Dennis Bridges returned to review of Receiving Design Updates - Google Drive slide presentation. Dennis is presenting updates that have been implemented based on changes to Stripes frontend. Usability approach to receiving was seen as cumbersome, so they implemented a lot of changes as a result.

"Receiving items": an order has been placed and is open, awaiting receipt of materials. Physical materials have arrived. Users is reviewing purchase order, and clicking 'Receive' from within FOLIO Orders app. "Receive" screen has not yet been implemented, because of changes to process. Dennis showed wireframes of what the window will look like. A select box has been added to Receiving screen; when one clicks on the box, a modal pops up that shows the specific items in that order, to make it easier to look for the specific items in each order, or each "Title". One can input a barcode as part of the receiving process, in this modal.

Kristin Martin asked for specifics about what's in a specific "Title" - will a "Title" be associated with multiple instances, especially in a range of formats? The point is that you can receive other than physical things. "Other" can include fees, and basically a grab-all for whatever the future might bring.

For an "Electronic" item - is that an electronic file? Or access being established to an electronic resource? Some institutions want to be able to record that electronic items have been saved. Martina Schildt said that many German libraries would like to be able to record that they're receiving an electronic copy. Kristen Wilson asked about behavior if there is no existing item record. Dennis said it's up to the user what records would be created. Many varieties of what would be possible here, especially if there is no item record. Some of this data does come from the item record - especially Barcode and Item Status - but Location is associated with holding.

Kristen Wilson asked about supporting automated receiving of high volumes of content - especially w/r/t significant shelf-ready titles. In these cases, an institution may not check every single item, but rather accept the vendor's statement that all the shelf-ready items have been delivered within a single shipment. Dennis said that it will need to be able to support that.

Dennis Bridges said some discussion remains regarding visibility and application of "Item Status" field - do people want to edit it here, or just see it, or not? Charlotte Whitt discussed how this data will work in other apps, especially the Checkin and Checkout apps.

Dennis Bridges brought up and worked through demo of Ordering process. A connection does now exist to Inventory so that additional bibliographic data is imported to Orders from Inventory. See the recording to view the demo.

Sara Colglazier asked questions about the manual input process, and the possibility of error introduction through this process. Charlotte Whitt pointed out that the goal here is to show the interaction between the various apps, and also noted that the "Instance status code" for these records is as "temp", so later, when the item arrives, catalogers will be able to apply full bib records over existing temp records. Kristin Martin said she expects that most of their records will be imported through bulk import process.

Conclusion
Meeting concluded at 9:30

Action items

  •  

1 Comment

  1. Hi all - I'll add this in the RM Slack channel as well, but wanted to address a couple of Sara Colglazier questions. The method Dennis showed (start in the POL, add minimal bib info, and then have it create the various instance, holdings, and item records) is definitely only one of the order methods we envision. There's the API that will trigger orders placed on a vendor website to be automatically created in FOLIO. There's also data import, which will allow incoming MARC records to create inventory records, order records, and invoice records. All of them are in development because we know that libraries have so many different ordering workflows. 

    Also, with regards to matching/overlay of better bibliographic data at point of receipt - the inventory will be aware of the POL as well as the vendor reference number (e.g. for GOBI, this would be the GOBI Order Key). If a bib record begins life as an OCLC record, Inventory will also be aware of the OCLC number, as well as other record ID and product ID numbers. When bringing in more complete MARC records via data import, any of those various product, record, or order IDs will be available for matching/overlay. For example, the incoming record may include the FOLIO POL, which is used to find the order line, and then its corresponding Inventory Instance, and then that Instance's corresponding holdings record, item record, and MARC record. Once those are identified, then the incoming data can update the MARC record (which in turn updates the bib data of the Instance), update the Instance (maybe with some tags, or with a cataloged date), update the holdings record (maybe with a call number), and update the item record (maybe with a barcode).