Libsafe v1.5.0 – What's New (February 2026)
This page describes what is new and improved in Libsafe v1.5.0. It covers new features you will see in the interface, behaviour changes that affect your daily work, and issues that have been fixed.
02 / February / 2026
v.1.5.0
What's new at a glance
Files and folders are now shown in Details (list) view by default, persisting across sessions.
The destination node is now shown before a Move In or Move Out action is executed.
The search field in reports is now case-insensitive, returning consistent results regardless of capitalisation.
The platform footer now shows the exact Libsafe version installed in each instance.
Two new real-time charts show the queue depth of the Ingestion Orchestrator and Ingestion Result Manager.
Ingestion processes can now be retried directly from the file detail panel and from Advanced Search.
The OCFL store can now be configured to use a separate S3 bucket, independent of the main Libsafe storage bucket.
Missing OCFL store configuration files are now created automatically from the platform settings on first use.
Fourteen issues fixed across login, navigation, ingestion, reports, copy, and archiving.
New features and improvements
Content explorer – Details view by default
When you open a container and browse its content, files and folders are now displayed in Details (list) view by default. This change persists across sessions — the Details view remains active even after you log out and log back in. You can still switch to other view modes manually during your session.
This is a platform-level default. Individual users can change the view during their session, but the next session will start in Details view again.
Structure Editor – clearer Move In and Move Out
The Move In and Move Out actions in the Structure Editor now show you the target node or new hierarchical level before the movement is executed. This makes it easier to confirm you are placing the node in the right position before committing the change.
How it works
Move In — when you select a node and use Move In, the system highlights the destination node so you can verify the target before the move takes effect.
Move Out — the new level the node will move to is shown before the action is applied.
Report search – case-insensitive
The search field available in all reports under Data Analytics → Reports is now case-insensitive. Searching for ".PDF", ".pdf", or ".Pdf" returns the same results. This applies to the Search field available in the Current tab of every report preview.
The search matches partial text within the searchable columns of each report. The columns that can be searched vary by report type and include fields such as container name, container ID, container description, file ID, filename, full path, metadata schema name, workflow name, and user email.
Platform version shown in the footer
The footer at the bottom of every page now shows the exact Libsafe version number installed in that instance. Previously, all instances showed the same version regardless of the release actually deployed. Each instance now displays its own version independently, making it easier to confirm which release is running in any given environment.
Ingestion monitoring – new real-time queue charts
Who this affects: administrators monitoring ingestion load in real time.
Two new charts have been added to the platform monitoring views, showing the current queue depth in real time for:
Ingestion Orchestrator — the number of items waiting to be dispatched to ingestion services.
Ingestion Result Manager — the number of results waiting to be processed and recorded.
These charts increase automatically as files are ingested, giving administrators a live view of ingestion load. They complement the existing Platform Processing and Performance charts already available in the monitoring section.
How to access the monitoring charts
Go to Administration → Performance Diagnostics.
The two new charts appear alongside the existing Platform Processing and Performance charts.
Retry ingestion processes from file detail and Advanced Search
You can now re-run one or more ingestion processes for a file without leaving the interface. This replaces the previous approach of writing directly to the service queue and allows retries to be triggered reliably through the web interface.
From the file detail panel
Open a container and select a file.
Open the file properties panel.
Locate the ingestion process you want to retry (for example, Hasher, Identifier, or Virus Scanner).
Use the retry action for that process.
From Advanced Search
Go to Advanced Search and filter for the files you want to process.
Select one or more files.
Use the retry ingestion action.
A retry will not start if there is already an ingestion step running for the selected file. Wait for any active ingestion to complete before retrying.
OCFL – support for a dedicated S3 bucket
Who this affects: administrators configuring the OCFL Archive storage layout. If your instance does not include the OCFL Archive, this section does not apply to you.
The OCFL preservation store can now be configured to use a separate S3 bucket that is independent of the main Libsafe storage bucket. Previously, the OCFL store had to share the same bucket as Libsafe content, which required versioning on that bucket. With this change, the OCFL store can reside in its own bucket — including buckets without versioning enabled — providing more flexibility in storage architecture.
This configuration requires administrator access and is set at the platform level. The OCFL bucket can be located at the root of the bucket or at a specific path within it. Contact Libnova support for setup guidance.
Both scenarios remain supported: the OCFL store can continue to use the same bucket as Libsafe, or it can use a dedicated separate bucket. This is a configuration choice per deployment.
OCFL – automatic store initialisation from settings
Who this affects: administrators setting up the OCFL Archive for the first time. If your instance does not include the OCFL Archive, this section does not apply to you.
When an archiving operation is attempted and the OCFL store does not yet have its required configuration files (the store declaration file, the layout file, and the extension configuration), the system now creates those files automatically using the values configured in the platform settings. Previously, missing configuration files caused the archiving process to fail with an error that required manual intervention.
The default OCFL store configuration values applied during automatic initialisation are:
OCFL version
1.1
Storage layout extension
0007-n-tuple-omit-prefix-storage-layout
These defaults can be reviewed and adjusted by administrators in Configuration → Settings under the OCFL settings group before performing the first archiving operation.
Bug fixes
Login – blank page after sign in
After a successful login, some users saw a blank page instead of being redirected to the home screen. The page now loads correctly after login.
Login – IP tracking for failed attempts
The IP address recorded for failed login attempts was sometimes shared across different users due to internal network routing. This has been corrected so that each failed attempt records the correct client IP, preventing one user's failed attempts from incorrectly blocking another user.
Navigation bar in Configuration
The breadcrumb navigation bar did not work within the Configuration section — clicking a parent item such as "Configuration" had no effect. Navigation now works correctly within the Configuration section.
Reports – Formats/Risk report error
The Formats/Risk report (Data Analytics → Reports → File formats/risk) consistently failed when executed. The report now runs and completes correctly.
Checksum validation – SHA1 and ADLER32 manifest files
Running the validation function on files with SHA1 or ADLER32 manifest types returned a regular expression error, even when the function trigger was correctly configured. Validation now runs correctly for these manifest types, consistent with MD5.
Advanced Search – not showing all results
When filtering by container in Advanced Search, the results did not include all ingested files. Only a subset was displayed. All files are now returned correctly.
Ingestion – files with + in the filename not ingested
Files or folders whose name contained the + character were silently skipped during ingestion — no error was shown and no files were processed. Files with + in the filename are now ingested correctly.
PREMIS events not registered correctly
PREMIS events were not being registered accurately in some cases, particularly when multiple copies of the same file were ingested concurrently. Some copies showed a full-text extraction success event when the content had not actually been indexed. PREMIS events now accurately reflect the actual result of each process.
Ingestion consistency – concurrent copies
When multiple copies of the same file were ingested simultaneously, some copies were indexed with full-text content and others were not, with inconsistent results. Ingestion now handles concurrent copies consistently.
OA_LINK metadata broken after copy
When an object that had an OA_LINK metadata field assigned was copied, the link in the copied object was broken. OA_LINK metadata values are now preserved correctly after a copy operation.
Archiving – error copying object to staging
Archiving processes failed with a stream error when the platform tried to copy an object to the staging area. The archiving process now completes correctly.
Archiving – Archiving Processes list not loading
The list under Content Processing → Archiving → Archiving Processes failed to load. The list now loads and updates correctly when filters are applied.
Container share – checkbox missing
The checkbox to mark content as shared was not visible on the container Shared tab. The checkbox now appears correctly.
TikaMeta – excessive memory consumption
The metadata extraction service was accumulating memory over time, eventually causing instability. Memory is now released correctly after each extraction task.
Summary of changes by role
End user
Content explorer opens in Details view by default; Structure Editor shows the destination before a move; login, navigation, and share checkbox issues resolved.
Administrator
New ingestion queue monitoring charts; OCFL can now use a dedicated bucket; OCFL store initialises automatically from settings; footer shows correct Libsafe version per instance.
Compliance / Audit
PREMIS events now accurately reflect process results; SHA1/ADLER32 manifest validation works correctly; report search is case-insensitive.
Operations
TikaMeta memory leak resolved; ingestion retry available from the interface; ingestion of files with + in the filename fixed; archiving process errors resolved.
Last updated