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
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.
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.