Page Comparison

Basic information on the requests app can be found here: https://docs.folio.org/docs/access/requests/requests/

Migrating using business logic

One migration path is to use FOLIO's business logic APIs to migrate your requests. The advantage of doing so is that the business logic APIs will handle things like creating notices

You can create requests by doing a POST to circulation/requests in mod-circulation: https://s3.amazonaws.com/foliodocs/api/mod-circulation/circulation.html

Title-Level Requesting and Migration

FOLIO supports title-level requesting, though it is in development with each release; your library should review the current functionality of title-level requesting for your planned FOLIO release and decide if you want to start with title-level requesting on or off.

The main consideration is that the first time title-level requesting is turned, FOLIO should have no open requests in the Requests app. 

The reason for this requirement is that title-level requesting requires managing queues of requests, and if there are open requests previously placed at the item level, there is no way for FOLIO to be able to determine how to manage the ranking and queues for title-level requesting on that associated instance.

So, if your library wants to use title-level requesting, it is much easier to use it from the beginning of when you first implement FOLIO in your production environment, because you can start that environment fresh and not have to figure out how to close out the request queue to implement title-level.

Migration to the correct request types 

FOLIO has three request types.

• Hold. The item has been requested and is not currently available.
• Page. The item has been requested and has a status of Available.
• Recall. The item has been recalled (shortening the loan period of the patron who currently has the item.)

If your ILS only has Holds and Recalls (such as Aleph or Voyager), you need to figure out how to logically split your holds into holds and pages for migration. FOLIO only allows you to create a hold if the item that is currently in circulation. E.g., if it's a hold on an item that's out, you can migrate it as a hold, but if it's a hold on an item that is returned and awaiting pickup to the user who placed the hold, it has to be migrated as a page.Request types are part of the request POST and depend on the item status and the allowed request types in the applicable request policy. That means that if you are using business logic to migrate, you need to determine the associated request type in order to form the API request.

If the request policy doesn't allow any requests to be placed, the request will be denied.

Migrating directly to storage

If your institution has migrated requests directly to storage, please add notes here as to your experience / tips for the process.