richard-churchman
5f6bbe45f7
Major bug fixes relating to the Redis implementation in Reprocessing and Search Key Cache were identified and fixed as part of the rekeying development. Included functionality to stop the Exhaustive training. Fixed the Unsupervised learning functionality in Exhaustive Training. Embedded the Mock Data CSV data into a class to make it compatible with Docker without needing to modify the Dockerfile (i.e, build). Included a new table that stores training data to enhance support capabilities for Exhaustive. Reintroduced and validated the Multitenancy functionality. Postgres is now fully deprecated in place of Redis for cache, and all implementations of the Interfaces for Postgres have been removed. No migrations exist to support this deprecation, and Postgres as a cache is now wholly unsupported. Removed the Indexing background thread, as Redis does not require it, given that it is a key-value pair database. Created a RedisCommandFlag Environment Variable to support Fire and Forget write to Redis in Invocation. Implemented functionality to Export, Peek and Download configuration environments using a secure, encrypted scheme. Created a permission to access the functionality via the user interface. Extensive database-based logging is included to provide for a comprehensive audit. Created functionality to Import the encrypted Export file inside a database transaction to ensure consistency. As Docker is now the primary deployment model, log4net instantiation has been moved to an approach that primarily uses programmatic instantiation of the ConsoleLogger and RollingFileAppender given Environment Variables. Implemented functionality to support remote \ mounted Log4Net XML Serialisation files for more advanced log4net configurations. Reintroduced access to counters via the user interface and created a permission. Took the opportunity to implement ReSharper linter suggestions. Disabled the Lock button across the whole application, with that functionality being reserved for future use. It is intended that locking happens programmatically on the basis of dependencies in future commits. Fixed several significant end-use bugs which became apparent during testing of the refactored code relating to case management and visualisations. Fixed certain other minor bugs that came up during testing. Brought documentation up to date for this commit. Brought the Docker Compose file up to date for this commit. Removed Redundant Environment Variables for this commit. Made the README file less verbose and unnecessary.
1.6 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Working Uploading and Recalling Files | 23 | Case Management | Configuration |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Working Uploading and Recalling Files
It is possible to upload files to a Case Key Value combination, with these files being centrally stored in the database.
Navigate to a case record via either Fetch or Skim:
Notice the Case Uploads tab:
Click on the Case Uploads tab:
In the case upload tab there exists a file upload pane, which will accept a dragged and dropped file, or the specification of a file location by clicking on the Select Files button:
In this example, click on the Select Files button, the Select Files dialogue box will appear:
Use the Select Files dialogue box to navigate to, and select a file, in this case an image:
The file will be uploaded and available in the database (not the file system):
select * from "CaseFile"
The file list is all files rolling up to the Case Key Value combination. To reference or retrieve an uploaded file, note firstly that the file name is a link:
Click the link:
The file will open up in a new browser tab is the content type is supported, else downloaded.