PureRed Filemaker & MS SQL
Overview
Requirements
The PureRed Connector is a custom adapter and can therefore only be used by PureRed. If you have special requirements for an adapter, please do not hesitate to contact us.
Requirements
The PureRed Connector is a custom adapter and can therefore only be used by PureRed. If you have special requirements for an adapter, please do not hesitate to contact us.
Typically username, password and specific system URL. Other parameters are also possible.
Automatic connection refresh (Basic auth) CI HUB saves the username and password (and eventually more login information like system-URLs) to refresh the connection automaticly.
A custom login page provided by CI HUB with input fields defined by the partner. As a rule, the following input fields are available:
- User name
- Password
- System URL (the URL which specifies which subsystem of the integration the user wants to connect to) further input fields are possible.
You can also search for a search term, that is in a metadata field. This simplifies your search. Images names could be very difficult, so for example there is a image with the metadatafield called "tree in the woods", with this search you can find this image far more quicker.
The CI HUB connector supports searching in the integration.
The search supports all options the integration is supporting via the API.
The content of the searchfield will be passed to the integration and the results will be shown.
The integration can deliver a "help" information that gives specific help for the search in the selected integration.
You can pre-filter your search results.
You can also filter by e.g., date.
Filters may be available in the folder navigation too.
The CI HUB Connector supports the use of different renditions/qualities of an asset. The API of the integration needs to support dynamic renditions. As default CI HUB always uses the "original" version. In addition the integration can deliver as example:
- LowRes version (a smaler version of the original)
- a JPEG (a different tecnical compression)
The list will be dynamic. So you see all renditions that are avail. based on your permissions and the integrations capabilities.
Custom Metadata (different per user or system) that is displayed in the "custom" section of an assets detail view.
The CI HUB panel doesn’t manage any user permission or logic regarding asset access etc. User access control is provided and managed entirely in the integration.
CI HUB Connector Feature Overview for PureRed Filemaker & MS SQL
This is a list of features for the PureRed Filemaker & MS SQL Integration
Typically username, password and specific system URL. Other parameters are also possible.
Automatic connection refresh (Basic auth) CI HUB saves the username and password (and eventually more login information like system-URLs) to refresh the connection automaticly.
A custom login page provided by CI HUB with input fields defined by the partner. As a rule, the following input fields are available:
- User name
- Password
- System URL (the URL which specifies which subsystem of the integration the user wants to connect to) further input fields are possible.
You can also search for a search term, that is in a metadata field. This simplifies your search. Images names could be very difficult, so for example there is a image with the metadatafield called "tree in the woods", with this search you can find this image far more quicker.
The CI HUB connector supports searching in the integration.
The search supports all options the integration is supporting via the API.
The content of the searchfield will be passed to the integration and the results will be shown.
The integration can deliver a "help" information that gives specific help for the search in the selected integration.
You can pre-filter your search results.
You can also filter by e.g., date.
Filters may be available in the folder navigation too.
The CI HUB Connector supports the use of different renditions/qualities of an asset. The API of the integration needs to support dynamic renditions. As default CI HUB always uses the "original" version. In addition the integration can deliver as example:
- LowRes version (a smaler version of the original)
- a JPEG (a different tecnical compression)
The list will be dynamic. So you see all renditions that are avail. based on your permissions and the integrations capabilities.
Custom Metadata (different per user or system) that is displayed in the "custom" section of an assets detail view.
The CI HUB panel doesn’t manage any user permission or logic regarding asset access etc. User access control is provided and managed entirely in the integration.
