Logs
While you will not be responsible for maintaining or regularly reading logs, it's important to know where they are and how to read them.
When you do any of the actions in the processing app, a log runs in the background, tracking what is happening and providing error messages if something gets stuck. If the job is completed correctly, you will receive a “Complete” message at the bottom of the log, and a Finished timestamp.
All logs can be found in the Logs tab of the Processing app.
There are some logs that will always appear at the top of the page:
Iiiflow.log
Error.log
Aspace-ingest.log (you can ignore this one)
Aspace-flask.log (you can ignore this one)
Below that will be the most recent, successfully completed logs, in chronological order.
The title will look like:
2025-07-11T09.48.12.250916-package- ua902.068_ HaG3KsFZuXefoXAaxsPbtb.log
Date Action Collection ID Package ID
A compilation of all the error messages will appear in the error log, if you want to investigate just the error, but it will also appear in the specific log of the job you were running (though it will not be saved to the logs file so if you close the window it will disappear).
You can take the error to an Archivist (Greg), or, if you’re feeling confident, you can try to read the original code and see where it goes wrong.
The UAlbany Github contains all of the various codes we use to process material, operate the website, and more.
The processing repository contains the processes relating to the processing app. The utilities folder contains the code relating to the different tabs on the processing site.
If you are uploading, you will want to check the “upload.py” document and if you are packaging the “packageAIP.py” document and so on.
The error message will tell you which line to look at specifically, such as:
“ /code/utilites/upload.py” tells us to look in the upload.py document in the processing repository
“Line 257” or “line 127” tells us to look specifically at lines 257 and 127 to see why/where the process is failing