- Installing and upgrading
- Installation overview
- General installation requirements
- Installing on Ubuntu Linux
- Installing on CentOS Linux
- Installing on SuSE
- Installing on Windows Server 2008 R2
- Installing on Windows 7
- Installing on Windows (Server)
- Installing on Mac OS X
- Installing on Synology DSM
- Configuring php.ini
- Configuring the database
- OpenOffice / LibreOffice
- OpenCV (facial recognition)
- Alternative installation
- User management
- Advanced user group options
- Customising ResourceSpace
An edit filter works like the search filters, but is used instead to determine if users in the group can edit resources based on the metadata in the resource. The existing 'e0' (or e1, e2 etc.) permissions must be used first to open up edit access. The edit filter is then used to restrict access to specific resources.
Filter builder support (version 9.3+)
From version 9.3 onwards, edit filters use the same filter building tool as search filters, provided that the following configuration option is enabled:-
$search_filter_nodes = true;
The creation of filters is described here.
Legacy filter syntax
See search filters for the legacy edit filter syntax if you are using ResoureSpace 9.2 and earlier, or if $search_filter_nodes is set to false.
For multilingual field options, the full i18n syntax string (e.g. ~en:Red~fr:Rouge) must be used here instead of a translated option.
Restrict by resource type
An additional feature for edit filtering only, is the ability to restrict editing by resource type. This is done by using 'resource_type' as the field name and the resource type reference as the value. For example, the following will restrict edit ability to resources of resource type 2 only (the default 'Document' type):
This can be used in combination with metadata filters.