Dash
Vendor: Bright Interactive
Overview
Requirements
Benefits
oAuth2 authentication makes sure the user grants access to his/her data on the data repository side without requiring CI HUB to even see or store user credentials. oAuth2 is the default auth. used by CI HUB. Depending on the capabilities of the connected system this can be a different implementation.
The connection is being refreshed automaticly by a so called "refresh token" delivered by the partner API. So to simplify, you dont have to manually log in again, after your connection has expired.
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.
Complex search querys means that you can use terms like "&" or "!=", etc. in the searchbar. The syntax is different for every 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 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.
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.
You can upload assets to the integration. If you select "(+)" from the CI HUB Connector, then you can upload to the selected folder. Some integrations do not allow uploading to the "root" folder. To select the asset to upload you can select from the active document/eMail or Timeline. Or you can select an asset from your local drive. CI HUB Connector also supports uploading of "snippets" "INDS". To upload a "snippet" just select 2 or more frames within InDesign and select (*). You can now upload the selected frames as "snippet". If you are uploading in InDesign and select a "INDD" filetype, you can also set the option to include a PDF and a ZIP Package to the upload. Some systems prevent uploading of "dublicates" please referee to your integration.
Update existing assets stored in integrartions. In case it is supported by the integration, the newly uploaded asset will be added as a new version.
Delete existing assets on the data repository. There is a little "Trashcan-symbol" in the panel, where you can delete the selected asset. There is a warning pop-up, where you have to confirm your action.
The "total asset count", counts the remaining assets that are found by your search parameters. Not every integration supports this function. The total asset count is displayed on the left side of the result panel.
You are able to add folders. Some integrations may not support this feature. At some integrations there is no use for it e.g., Stockprovider.
You are able to delete empty folders. Same here. Some integrations may not support this feature. At some integrations there is no use for it e.g., Stockprovider.
Custom Metadata (different per user or system) that is displayed in the "custom" section of an assets detail view.
Any selected asset can also be opened at its "original" location. If the integration supports the "Open in Browser" link, then the CI HUB Connector opens the selected asset within a browser at its original loaction.
This main feature includes several subfeatures:
- Relinking all placed assets and update link status
- Multiple matches with versions of an asset
- Upload function support
- Upload parameter support
- Status check
- Relink an asset with or without conversions
- Notification sign, if newer asset is available
- Resizable thumbnail preview of a version of an asset
- Clicking the blue link in linkpanel metadata section leads to highlighting asset in document
- Highlighting assets in document/workspace leads to highlighting related asset in linkpanel
- Relink an asset with other versions of the same asset
The business logic means the following: For example, there is a rights system on the partner's website, i.e. some users can do a few things more than others. For example, if we have a user who does not have any rights in the web frontend, but who can still do everything in the CI HUB panel in this integration, then the user-defined business logic comes into play. This is implemented by CI HUB and ensures that rights are properly managed.
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.
Assets bigger than 1 GB can be uploaded via ci hub panel.
oAuth2 authentication makes sure the user grants access to his/her data on the data repository side without requiring CI HUB to even see or store user credentials. oAuth2 is the default auth. used by CI HUB. Depending on the capabilities of the connected system this can be a different implementation.
The connection is being refreshed automaticly by a so called "refresh token" delivered by the partner API. So to simplify, you dont have to manually log in again, after your connection has expired.
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.
Complex search querys means that you can use terms like "&" or "!=", etc. in the searchbar. The syntax is different for every 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 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.
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.
You can upload assets to the integration. If you select "(+)" from the CI HUB Connector, then you can upload to the selected folder. Some integrations do not allow uploading to the "root" folder. To select the asset to upload you can select from the active document/eMail or Timeline. Or you can select an asset from your local drive. CI HUB Connector also supports uploading of "snippets" "INDS". To upload a "snippet" just select 2 or more frames within InDesign and select (*). You can now upload the selected frames as "snippet". If you are uploading in InDesign and select a "INDD" filetype, you can also set the option to include a PDF and a ZIP Package to the upload. Some systems prevent uploading of "dublicates" please referee to your integration.
Update existing assets stored in integrartions. In case it is supported by the integration, the newly uploaded asset will be added as a new version.
Delete existing assets on the data repository. There is a little "Trashcan-symbol" in the panel, where you can delete the selected asset. There is a warning pop-up, where you have to confirm your action.
The "total asset count", counts the remaining assets that are found by your search parameters. Not every integration supports this function. The total asset count is displayed on the left side of the result panel.
You are able to add folders. Some integrations may not support this feature. At some integrations there is no use for it e.g., Stockprovider.
You are able to delete empty folders. Same here. Some integrations may not support this feature. At some integrations there is no use for it e.g., Stockprovider.
Custom Metadata (different per user or system) that is displayed in the "custom" section of an assets detail view.
Any selected asset can also be opened at its "original" location. If the integration supports the "Open in Browser" link, then the CI HUB Connector opens the selected asset within a browser at its original loaction.
This main feature includes several subfeatures:
- Relinking all placed assets and update link status
- Multiple matches with versions of an asset
- Upload function support
- Upload parameter support
- Status check
- Relink an asset with or without conversions
- Notification sign, if newer asset is available
- Resizable thumbnail preview of a version of an asset
- Clicking the blue link in linkpanel metadata section leads to highlighting asset in document
- Highlighting assets in document/workspace leads to highlighting related asset in linkpanel
- Relink an asset with other versions of the same asset
The business logic means the following: For example, there is a rights system on the partner's website, i.e. some users can do a few things more than others. For example, if we have a user who does not have any rights in the web frontend, but who can still do everything in the CI HUB panel in this integration, then the user-defined business logic comes into play. This is implemented by CI HUB and ensures that rights are properly managed.
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.
Assets bigger than 1 GB can be uploaded via ci hub panel.
Don’t search, just use.
CI HUB connects all kinds of brand assets spread across various locations to the relevant people. Assets become easily available in your favorite creative or productive applications. This makes you even more creative and productive and improves efficiency and accuracy.
