Have a question or a comment you'd like to see added to this FAQ? Please use this form to submit them.
- FOLIO Analytics Report Repository?
- How do I know which apps I will need to do my job?
What you can do is based on what you were able to do in Voyager. It's confusing because the names are different, but when you get your account you'll have access to the apps you need. As procedures across the library are updated, you should also be able to find information there about which apps to use for what. What is the difference between the Instance and the Item tab?
In FOLIO, Instance records are the equivalent of Voyager Bibliographic records. Item records in FOLIO are basically the same as Item records in Voyager. The Instance record identifies the work (Title/edition/format), and the Item record identifies the specific copy in our library. When searching in the Inventory app, you will see options to search by Instance, Holdings, or Item. If you pull up an Instance record, you will see the attached Holdings (e.g., Law Library KF3425 L42 2004) and Item (c. 2 + barcode) in the details.
You can do the same keyword search in each segment (Instance/Holdings/Item) but limit your results by different facets, depending on the record type. There are also some different search options, depending on which segment you choose.For example, in the Item segment you can search by barcode and you can limit by the item material type- FOLIO is a modern web application that is
- more intuitive interface than Voyager
- being web-based we don't need to install special clients on devices in order to use it, no need to use remote desktop to log in if working remotely
- you can bookmark things you access regularly
- don't have to toggle between modules (since everything is all in one place)
- modern APIs will make some integrations and automation easier
- extended API will allow for fuller + tighter integrations with other systems
- From a cataloging/metadata perspective, the biggest thing is the option to have descriptive records that are not in MARC format
- Will allow us to create records for circulating equipment, for example, without having to use MARC
- In future, it will mean more flexibility for our bibliographic description including a possible smooth path to linked data cataloging
- For special use cases like RMC’s ArchivesSpace integration we can create fields in FOLIO that reflect the actual data, rather than forcing it into predefined Voyager fields
- Better control over user permissions through the ability to give users more than one permissions set
- More control over notices
- Will be much easier to update settings (as we've been doing with fines/fees settings in Voyager on an ongoing basis since last March with much difficulty)
- In-app report capability that we don't have in Voyager (as well as separate reporting like Voyager from LDP)
- Creating new locations will be much easier
- E-Resource management will be done in FOLIO alongside acquisitions.
- This will reduce some double-entry and will enable us to more effectively connect payment information to the specific resources being paid for.
- One sneaky big thing: it's much easier to copy barcodes!
- And some small stuff:
- FOLIO will automatically forgive fines/fees when a Lost item is returned
- Can look patrons up by NetID from more places
- Patrons won't be able to place holds on available items any longer
- Something can't be "missing" if it's checked out (which is logical: if it's checked out, we know where it is).
- FOLIO is a modern web application that is
- How will I know how much I need to learn in FOLIO and when I have to learn it?
- Will there be an opportunity for small group (less than 10) training sessions?
Yes, there will be small group trainings for Iris, our FOLIO go live version, in May and June. - What kind of permission settings have we got to work with? Will there be view-only? Who can set permissions?
There's a committee working on permission sets based on what people could do in Voyager. It's not a straightforward "translation" from Voyager to FOLIO and during this training period we're getting lots of helpful feedback for what isn't working as expected. We've created a view-only set for those apps you don't need to make changes in. - How are we going to get access to old Voyager information, such as past invoices and PO notes on completed POs that won't be migrated to FOLIO?
- Can we get search function tips and tricks for FOLIO?
Guidance for searching within Inventory
Local (CUL) Inventory Search documentation - Is there a glossary?
Glossary of FOLIO Terms - As FOLIO keeps changing/adding features, how will we know when something new is coming?
CUL has representation on the FOLIO Product Council, and Gerald is active in the Open Library Foundation Community. CUL staff will continue to participate in FOLIO SIGs. Additionally, we are creating a CUL FOLIO Steering Committee, as required by Cornell IT Governance. This committee will have representation from across CUL and will be responsible for keeping an eye on the FOLIO road map and communicating it to CUL. - How will FOLIO interact with OCLC? Do we know yet how it will interact with ArchivesSpace? How about Aeon?
- FOLIO provides a mechanism for those working with bibliographic records to import from OCLC. Additionally, we are in the process of rebuilding batch workflows that send and receive changes from OCLC on a nightly, weekly or monthly basis.
- For ArchivesSpace we expect the interaction to be pretty similar with what we have currently with Voyager. In March we plan to begin testing the thrice weekly load of ArchivesSpace changes into FOLIO, mirroring what we do in Voyager. For Aeon, much of the integration relies on Blacklight. We've engaged with Discovery and Access to start exploring what updates need to be made. Reach out to Jenn (jrc88) or Erin (eef46) if you have questions.
- How long for the new bib in FOLIO to show up in the public catalog? and can it be suppressed from the public catalog?
- As with Voyager, changes to bibs and newly created bibs should make their way to the public catalog in a matter of seconds between 3:30 am and 9 pm, with nighttime changes making their way to the public catalog once updates resume the following morning. The exact timing may evolve, but the responsiveness should be comparable.
- Yes. Each instance (derived from a bib), holding, and item record in Folio has a Suppress from discovery flag which will block that record from being visible in the public interface.
- As with Voyager, changes to bibs and newly created bibs should make their way to the public catalog in a matter of seconds between 3:30 am and 9 pm, with nighttime changes making their way to the public catalog once updates resume the following morning. The exact timing may evolve, but the responsiveness should be comparable.
- Is a Block to be used when items are not returned by due time since we are no longer fining for items returned late?
On a system-wide level, we are going to shorten the amount of time that it takes for a reserves item to have a “lost” status applied to it from three days to two. This means that once an item is two days overdue, the patron will be charged a $150 replacement fee. Patrons are automatically blocked once they accrue $300 in fines and fees, so anyone with two or more reserves items that are two or more days overdue will be unable to use the library until they return the overdue materials. We are also going to increase the frequency of our overdue notices.Individual units are free to institute additional policies as they deem appropriate, which could include using manual blocks to impose restrictions on patrons who abuse our policies (such as by regularly returning materials late).
- Will FOLIO store records of last check-in transaction record like Voyager does on items? Last transaction record is often used when searching for pages to determine if it was recently received by the library or has not been used for a long time.
Yes. The last transaction can be found at the bottom of the item detail screen, containing the date, time, location and user. It also possible to see transactions on an item via the Circulation log app.