If a container is stored at LINX, add the following information to the Aeon request (case sensitive):

• Delivery stop: sc
• Offsite location: STOR
• Barcode

Ensure there are no leading or trailing spaces in these fields.

After adding these fields or confirming that patron-provided information is correct, save the record and then route to the appropriate "Awaiting Retrieval from LINX" queue.

Tip: clicking print callslip automatically routes the request to the Awaiting Retrieval from LINX queue. Do not print the callslip until the request is ready to be sent to Caiasoft.

When a container is ready to be returned to LINX, identify the Aeon request that was used to send retrieval information to Caiasoft. This can be confirmed by checked the request history.

If the container is being placed on a holding shelf, route the request to Awaiting Return to  LINX.

When the container is placed on range 29 in Shipping & Receiving compact shelving, route the request to In Transit to LINX.

If a specific Aeon transaction was not used to send retrieval information to Caiasoft, route that Aeon request to Request Finished.

Five minutes after submitting a request for materials from LINX in Aeon, check the request queue to make sure that the request went to a "Request Received by LINX" queue and did not error out. If the request could not be processed due to an error, open the request to troubleshoot. Expand the notes section at the bottom left of the request screen for more information on the specific error. Note that if there are multiple errors, Aeon only displays the first error it encounters.

**Tip: if you cannot see the portion of the screen containing details on the error messages, make sure you expand the Aeon request window to full size.

Common errors include:

• A missing or incorrect barcode
  • To resolve: double check the barcode in ArchivesSpace or Caiasoft, add it to the Aeon transaction in the "Item Barcode" field, save the Aeon transaction, and then re-route to the appropriate Awaiting Retrieval from LINX queue
• A missing or incorrect storage location code
  • To resolve: add or correct the storage location to STOR. Note that this field is case sensitive. Save the Aeon transaction, and then re-route to the appropriate Awaiting Retrieval from LINX queue
• A missing or incorrect delivery stop code
  • To resolve: add or correct the delivery stop code. The most common stop code used is sc.Note that this field is case sensitive. Save the Aeon transaction, and then re-route to the appropriate Awaiting Retrieval from LINX queue
• A request for a container that has already been delivered to Mullins
  • To resolve: search by barcode in Aeon to locate the previous transaction and determine where the materials are. Route the new request to "Item Checked Out."

Aeon is not currently used to send new accession jobs to Caiasoft. To accession new top containers to LINX, refer to the Processing Manual.

• To request top containers for deaccession from LINX, staff may either create requests manually or by using the spreadsheet upload method. Fill in all the fields you would for a typical request of a box from LINX, including the MC number, collection title, container number, barcode number, stop location (sc), and offsite storage location (STOR).
• When you have filled out and saved your request, do not click the print callslip button as you would for a normal request. Instead, manually route the request to “Awaiting Retrieval from LINX for DEA.”

• The system will communicate this to Caiasoft; your job status will be updated to “Request Received by LINX for DEA” once it’s shown up in Caiasoft as an external retrieval request circulation job.
• LINX staff will then apply the request stream to a job and send the boxes to Mullins. Your Aeon job status will be updated to “In Transit from LINX for DEA.” Unless you have alerted LINX staff that this is a high priority, they will continue to prioritize researcher requests, it may take several days for the job status to move from “Request Received” to “In Transit.”
• Once you have received the boxes from LINX, route the Aeon requests to “Item Checked Out to Staff” and then to "Request Finished." If you are sure that you will not be returning the exact same boxes and barcodes to LINX, you can go ahead and route to “Request Finished.”
• In ArchivesSpace, go to the top container management module and change the location of all the boxes from “STOR” to your processing area or the area where you are storing the boxes during your project.  

Note: this workflow documentation was created by Katrina Windon and is cross-posted from the Processing Manual.