How Can We Help?
File storageFile storage
Pure can be configured to store files on the local file system or in external repositories.
Creating a storage
Storage configurations for different types of repositories can be added, and the type of content to synchronise can be defined. Additional filters can be specified to further filter out content. This is all done in Administrator > Storage > File storage. Use the dropdown to select the storage type.
Conditions for storage
The conditions for storage section in the the store configuration is used to specify what content the store should hold.
The following filters are available:
| Storage filter | Description |
|---|---|
| Confidential content | Makes sure that content marked as Confidential is transferred. |
| Content visibility | Define the level of visibility for content to be transferred. |
| Publication state |
Define the publication state, e.g. only Published, or also E-pub ahead of print, or any other values. Only available for Research outputs. |
| Type classification | Limit the transfer to specified types of the selected content type, e.g. only Articles. |
| Workflow | Define which workflow steps the content must be in before it will be transferred. |
| Electronic version access |
Define access level for electronic version. Note, embargoed files are treated as 'Open' when the embargo date has passed. Only available for Research outputs. |
| Enable file embargo check |
Enabling this will prevent embargoed files from being transferred. Only available for Datasets and Student thesis. |
The files and metadata for content will be stored in all stores where the conditions match.
If the conditions between stores overlap, a copy of the files and metadata will be transferred to each store.
Re-configuring a store
If an existing store is re-configured, for example by change of visibility on filters, the files will be added/removed to the storage. The system will move the existing files according to the new rules on the next full Preserved Content Update Job run (each night), and modified content will be moved when then job performs one of the incremental runs.
Default storage
All files that does not match the conditions for storage on any store is stored in the default storage. By default the Local file storage is configured as the default store, but another store can be configured as the default store.
Because the default store needs to be able to store files for all content types, only Local file system and Amazon S3 stores can be configured as the default store.
Changing the default store can result in a lot of file being moved.
Temporary storage
When new files are uploaded to Pure, they are first stored in temporary storage. Later the Preserved Content Update Job moves the files to other stores according to the conditions for storage.
Testing configuration
The test button validates the configuration, and attempts to contact the server to verify the URLs, credentials, and other configuration options to the extent possible by the repository API.
Analyse impact
The Analyse impact function displays an estimate of the changes the current configuration will have on content stored in the storage. Modifying the conditions for storage can cause content to be added or deleted from the store, and the Analyse impact dialogue will display the estimated number of addition, updates, and deletions.
Disabling file synchronisation
For testing purposes a storage can be set to read-only mode by switching off Enable content writes to this storage. The Preserved Content Update Job job will skip synchronisation of all content that would otherwise be updated, deleted or created in the storage.
All file synchronisation can also be turned off by starting Pure with the -DdisableFileSynchronization=true command-line option. This prevents the content update job from running, and allows administrators a chance to validate the storage configuration before any synchronisation takes place.
Deleting a store
Only empty storages can be deleted. To empty a storage remove all conditions for storage, and let the content update job move any stored content away from the store.
Storage specific options
Local file system
For more information about storing files in the local file system with Pure see the Local file system specific documentation
Dspace
For more information about using Dspace with Pure see the DSpace specific documentation
Eprints
For more information about using Eprints with Pure see the Eprints specific documentation
Amazon S3
For more information about using Amazon S3 with Pure see the Amazon S3 specific documentation
Published at March 26, 2025