OLE does not have claiming functionality. Claiming reports were in development, but never completed. Fields still need to be filled out (action interval and action date)
Whoever sets up the serials claiming record sets up the Enumeration and Chronology
Main receipt history - each record has a public display check box. If checked, the issue shows in the newly received issues catalog area.
Information for the last issue received remains - update that with new information. Can also change receiving pattern at that time.
Because the fields are free text, there is a lack of consistency, but once bound, the inconsistencies won't show to the public any more.
Current method of claiming - fill out a Google form which is submitted to serials staff.
If received out of order, the display is not in chronological order - public display out of order too.
Receiving record type (main, supplemental, index) not currently available in FOLIO - hopes that this will be done in FOLIO.
OLE has separate summary of holdings records which are updated when issues are bound. Each serials receiving record has a "public display" box - if checked, any new checkins are displayed and added to the holdings record.
Binding issues requires manual editing of serials receiving and the holdings record.
Is possible to "unreceive" items - completely deletes the issue from serials receiving (not their practice).
There is some more information under the "details" link
Action Interval and Action Date are required if the claim box is checked in OLE. Reports were never developed which would take action on the interval and date above.
Dennis Bridges - Shared slides about how FOLIO is thinking about implementing receiving.
Currently implemented:
Order record - check box for "manually add add pieces for receiving"
From the order record - Open order, once it's opened, choose edit and receive. or could use the receiving app to search for titles and add pieces.
From receiving app, click add piece, fill in modal that shows caption, piece format, expected receipt date, location, comment. Can create an item from the modal. Can also indicated that the piece is a supplement. (currently there are no other descriptions than supplement).
Some things that are planned - mockups of screens:
Ranking has slowed down momentum in implementing these features
UXPROD-194 - Checkin Maintenance - option to describe a checkin pattern and details
In Receiving app, looking at titles and the expected or received items - a button for "manage pattern"
momentum began to slow here, so that's the last mock-up that was created
UXPROD-2373 - Allow display of piece on holding record - May have toggles on piece information to display to the public, or to add to the holding. May include caption and location as well.
Q - Do we have any plans for multiple tenants? Acquisition units that may help with that. Shanghai will be using multi-tenants, each library may want to be responsible for their own receiving records and not see other's receiving records? A user may have permissions to create/edit/delete invoices, but if an acquisitions unit is added, the permissions would be restricted to just the acquisitions unit to which the person is assigned. Affects Orders, Organizations, Finance apps. Hasn't been expanded to Receiving app yet, but could be.
Q - How are batch renewals handled? No current batch renewal functionality in FOLIO. Orders can exist over multiple fiscal years. Can invoice against that order year after year. There is a renewal interval for the order, but the system is not automated for that process yet.
Q - How is data received from vendors? MARC data comes in through data import - can create multiple
Currently creating instance, holdings, items - working on Edifact, working on adding order data after that.
Q - Is there a way to manage a vendor catalog through FOLIO. Could create a link in the vendor record to the catalog, order through vendor system and then load records into FOLIO
Q - How are bound volumes managed in FOLIO? Will vary depending on library. Will need to end up with something similar to OLE where the individual issues show as checked-in, then when bound, the bound volume is part of the permanent holdings, and the individual issues would stop showing on the holdings
Q - Will we have a serials module in the future? Or will the functionality be spread across the other apps. Likely Invoices in Invoices, Orders in Orders, Receiving in Receiving.
Would be interesting to have a workflow driven process for the serials process. TAMU did work with mod-workflow for their migration. Need more time and developers to work on the workflow app.
Recording of Webinar from Shanghai Public Libraries