iBase Trinity - digital asset management and multimedia online library

Section map : Summary - Features Guide - Details - Prices

4. Configurable database

6. Asset file types

Jump to page

• 1. Capacity & storage
• 2. Optional features
• 3. Google indexing
• 4. Configurable database
• 5. Multiple source databases
• 6. Asset file types
• 7. Uploading
• 8. Keyword / Tag / Subject hierarchy
• 9. Collections
• 10. Editing metadata
• 11. Searching data
• 12. Federated Searching
• 13. Branding - look and feel
• 14. End user search interfaces
• 15. Displaying embedded HTML
• 16. Watermarking
• 17. Asset requests
• 18. Online ordering and E-commerce
• 19. User feedback
• 20. Access control and user permissions
• 21. Audit trail
• 22. I.T. Environment
• 23. Language
• 24. Working with videos
• 25. Sharing Digital Media on social networks
• 26. Working with documents

5. Multiple source databases

As many separate and completely independent source databases as are required can be created. All of the features described here are applied to each independently, and will have their own user logins and permissions, their own data forms and workspaces etc...

Multiple Web / intranet destinations

From a single source database records and assets can be published independently to any number of separate web or intranet sites. For example, you might have an internal iBase Trinity on your intranet to which all of your images or other digital assets are available with all of the metadata, and a public web site on which you want to present a sub-set of the records, perhaps with only some of the metadata fields on view.

One of the Trinity sites could be for a public access kiosk in a gallery or museum. At one time such systems had to be specially designed with extremely simple touch screen interfaces suitable for people with no experience with a mouse or keyboard. However, nowadays it is rare that potential users of a kiosk do not have sufficient skill with a mouse and keyboard. There are two significant advantages of this circumstance:

• 1. Users are not necessarily limited to only basic functionality, such as would be available from a touch-screen or similar interface without a keyboard.


• 2. Where an organisation requires a website providing essentially the same features as a kiosk, it is not only possible but also highly cost effective to use the same software for both requirements. Any differences between the web system and the kiosk can be accommodated by configuration.

Not only is this approach very cost effective for initial implementation, but of course it also means that any changes made for one application will, if required, also be available to the other at no additional cost.

Back to summary and index or top of this page

PDF version of all digital asset management topics