Document Store v2026.1.1 Release Notes

Summary

This release of Document Store is for the integration of USxS and Inventory applications.

Important Highlights

• Integrate Document Store into USAS, USPS and Inventory. With this release Document Store is available to integrate with USAS. Nothing in the UI will change until the Document Store module has been enabled and the migration of files has been scheduled. We understand this is a very busy time of year with all of the Calendar Year End activities and we anticipate most will not attempt this prior to training. As requested, training for ITC staff only will be offered on Feb 20, 2025. If you would like to process a test migration ahead of the training, the technical documentation is provided below.

• Technical Guidance

  • MCOECN Hosted

    • Post Install Procedures

  • Technical documentation for self hosted ITCs

    • Document Store Installation Guide

    • Backup/Restore Document Store

    • Document Store General Troubleshooting

  • Document Store DB size will be larger than the size of the file archive due to indexing. Prior to running a migration you should run the following query which will provide values for the total object count in the File Archive, the database size and the large object (LO) size. These values can help determine resource needs, see Important note below. Running this query both before and after migration will show you the impact of the migration on the core database.

    • Using the System/DBA option, change type to SQL and paste the following text into the query area and click Go.

      • SELECT (SELECT COUNT(*) FROM fs_filestore) + (SELECT COUNT(*) FROM fm_fileset) + COUNT(*) AS total,
        pg_size_pretty(pg_database_size(current_database())) AS db_size,
        pg_size_pretty(pg_total_relation_size('pg_largeobject')) AS lo_size
        FROM fm_filecategory;

      • This query result will provide 3 values in the results table

        • column 0 is the total object count

        • column 1 is the current db size

        • column 2 is the LO (large object) size.

        • See the table below to determine estimated migration time.

    • Important: If the total of the USAS and USPS LO size * 1.5 exceeds the size of the “data” directory (/usr/share/elasticsearch/data) you’ve allocated, additional resources will be required prior to starting the migration for that district.

      • MCOECN hosted: contact DCO team for assistance increasing Document Store disk space prior to starting migrations. By default that directory is 200 GB.

      • Self hosted ITCs: increase Document Store disk space and restart application prior to starting migrations.

    • projected size approximately 50%

• How long will the migration take? This depends on several factors: total object count, large object size (LO), and instance memory.

  • SSDT recommendation: for districts that fall in the less than 2 hours, most migrations can be run in the evenings. For larger districts the recommendation is to run the migrations over the weekend.