<< back to results



TopTechPhoto


Notice: All information has been provided by the vendors themselves.

Profile Navigator

Vendor Details

Contact Name
Konstantin Shtondenko
Company Profile
TopTechPhoto is a software development company with strong focus on imaging.?

We've developed the most popular online raw converter (see it at http://raw.pics.io) and the service Pics.io, that turns Google Drive into a full-fledged Digital Asset Management system.?

Contact Telephone
+380672519415
Contact Email
john@toptechphoto.com
Company Website
http://toptechphoto.com
Years Trading
5
Office Locations
  • 641 Lexington Avenue, 14th Floor New York, New York 10022
  • Kosmicheskaya str. 21, Kharkiv, Ukraine
  • Product Name
    PICS.IO
    Latest Version Number
    1.80.1.0
    Date Of Last Release
    27/04/2015
    Documentation URL
    http://support.pics.io/knowledgebase/articles/566298
    Online trial link
    http://pics.io/digital-asset-management
    Company LinkedIn URL
    https://www.linkedin.com/company/2369452?trk=tyah&trkInfo=clickedVertical%3Acompany%2Cidx%3A2-2-5%2CtarId%3A1430151107850%2Ctas%3Atoptec
    Company Facebook URL
    https://www.facebook.com/toptechphoto
    Clients & Customers
  • OsbornBarr, Arriba! creative agency, Vintage
  • Partner Network
    If the vendor operates through a sales channel they may use intermediaries who have regional focus or additional specialisms in a given vertical market.
  • No
  • Licensing

    Licensing Model
    This refers to the type of licence the DAM system software is supplied under. Proprietary means that the developer restricts access to the source code (the instructions used to generate the software). Open source means that the developer provides full access to the code so you can modify it yourself. Split model is hybrid and means they may offer both options with some restrictions removed (or added) depending on the model chosen. If split is selected, it is advisable to verify the differences with the vendor.
  • Proprietary
  • Licence Notes
    Up to 10 users: $100/month ($1000/year) Up to 50 users: $400/month ($4000/year) Up to 100 users: $700/month ($7000/year)

    Use of Open Source Components
    Many DAM systems use freely available open source components to deliver key functionality. The products themselves may not be open source, however. This question will help to identify to what extent they are open source.
  • Some open source components used, but core product is not open source
  • Hosting

    Software Delivery Methods
  • Installed (On-Premise)
  • Cloud/SaaS
  • Technology

    Client
    Client refers to the type of hardware or software device that can be used to access or control the DAM system.
  • Web client
  • Client Notes
    There's a mobile interface of web client.

    Server Operating Systems supported
    This only applies for installed or hybrid DAM systems and refers to what types of OS they can be run on. This question is less relevant for DAM systems where a third party will be hosting it for you.
  • Not applicable
  • Web Server
    The type of web server software that the DAM system can operate with. Not all DAM systems use a web server and for pure SaaS products the question is irrelevant. If you either want SaaS or non-web DAM systems, do not choose an option.
  • Other
  • Software Development Technologies Used
    This means the programming language or development technology used to implement the DAM system. This question is more important for open source software or if you have IT policy restrictions that require you to use (or not use) some technologies. It may not be relevant if you require a hosted DAM and never intend to host the system in-house.
  • Other
  • Search Technologies
    This refers to third party search components that the vendor uses to provide the text search features (and sometimes other related search functions).
  • Other
  • Service Oriented Architecture
    Service Oriented Architecture (SOA) means the vendor's product uses a modular architecture where each core DAM function is delivered as a service which can be separated out independently from other functions. It is important for large-scale Digital Asset Management implementations or more complex integration requirements.
  • Yes
  • Unique SOA Services
    If the vendor uses a Service Oriented Architecture, they should be able to identify a number of unique services that are isolated from each other. Note there is overlap between with question and the one about scalable asset processing. Some vendors do not have an SOA but do offer large scale asset processing capabilities.
  • Metadata
  • Service Oriented Architecture Notes
    Custom fields functionality allows to add any metadata field an organization needs.

    Search

    Search Features
    This describes the search strategies that can be used to find assets. If you do not understand any of them, leave the options de-selected. Most DAM systems should support at least keyword search at a minimum.
  • Keyword
  • Filters
  • Search Notes
    Full-text search: title, description, keyword, custom field.

    Index/Search Text Content Of Documents
    Some DAM systems can search the text content of document assets and that might be important for your DAM solution.
  • No
  • Document Text Indexing Notes
    But it does Google Drive.

    Metadata

    Embedded metadata support (reading)
    Embedded metadata refers to information stored within asset files which can be searched from the DAM system. There are different standards for this type of metadata. Some image cataloguing software like Adobe Lightroom will write this data to asset files and a device like a camera may capture details also such as GPRS coordinates where an photo was shot. XMP metadata is often used with other types of files such as InDesign or PDF. If you are unsure whether this applied to you, do not check any options.
  • EXIF
  • Embedded metadata support notes
    Partial EXIF for raw images

    Controlled Vocabularies
    Controlled Vocabularies are predefined lists of search terms. They can be realised in many different ways but the common factor is the user picks from a restricted selection rather than enters a keyword. Most DAM systems will usually support both controlled vocabularies and keywords.
  • No
  • User Defined Metadata Fields
    The ability to configure metadata your own metadata fields is important for DAM systems so you can assign a dedicated field for certain items of information rather than using a generic classification method or one of the vendor's own standard fields.
  • Yes
  • Cataloguing Interface Options
    When cataloguing assets with custom fields, some metadata will be controlled selections, others will be free text. There are further choices like date fields, file attachments etc.
  • Text field
  • Checkbox
  • Date
  • Business Intelligence & Reporting

    Asset Usage Records
    To enable reports to be generated, DAM solutions must retain records of asset usage, including searching, download and editing of records. The reporting should include the user who carried out the activity and the date/time it occurred.
  • No
  • Audit Trail
    A detailed audit trail that logs every user action in a central record is useful to gain insight into user behaviour. Comprehensive audit trails allow DAM system users to produce reports that address their unique needs.
  • Yes
  • Audit Trail Notes
    Uploaded versions, discussions.

    Built-In Reports
    A range of built-in reports that you can quickly generate is useful to answer common questions such as the "what is our most popular asset?".
  • No reporting features
  • Asset Processing

    Dedicated/Scalable Proxy or Derivative Asset Generation
    Nearly all DAM systems will generate thumbnails and previews of media, including more dynamic types like video or audio. Some products use a separate server to do this which usually makes them more suitable for large scale asset ingestion and processing.
  • Yes
  • Dedicated/Scalable Proxy or Derivative Asset Generation Notes
    That part is handled by Google Drive.

    Multi-Page Document Asset Previews
    If you deal with document oriented assets, having a solution which can generate multi-page previews (and also zoom in on them) can save the hassle of downloading a file only to discover it is not the one you need. For assets with very similar content, this can be a useful feature.
  • No
  • Asset Manipulation

    Image Manipulation
    Many DAM systems allow users to manipulate images by resizing, cropping etc. Choose any features which are important to your users.
  • Image re-sizing
  • Image cropping
  • Format conversion
  • Flip images
  • Rotate image
  • Effects & filters
  • Batch manipulate groups of assets
  • Video Manipulation
    Some DAM systems may allow video assets to be converted or modified. If that is a potential requirement for you, specify those features which are likely to be needed. EDL = Edit Decision List and refers to providing in/out points when editing video footage.
  • No video manipulation features
  • Integration

    API
    API means Application Programming Interface and allows third party software to control a DAM system. If you intend to integrate your DAM with another existing solution then you need to choose the API protocol that is compatible with that.
  • None
  • Storage Integration
    Many DAM solutions will now allow assets to be stored on the server of Cloud storage providers. This allows asset files to be distributed and/or integrated with other solutions. Some third party services use generic protocols like FTP, others are proprietary.
  • Google Cloud Storage
  • Storage Integration Notes
    Google Drive

    Scripting & Plug-Ins

    Scripting Capabilities
    Some advanced DAM solutions have a scripting capability that allows users or third parties to add functionality which the vendor did not originally envisage. Usually programming skills will be required to use this, but some tools have visual interfaces also.
  • No
  • Plug-In Support
    In addition to scripting (or sometimes instead of), some DAM solutions will have a plug-in architecture that allows third party developers to extend the core platform.
  • No
  • Authentication

    Authentication Support
    If you need to integrate with an existing corporate authentication service then this option will be important for you.
  • None
  • Multi-Lingual Options

    Multilingual Application Interface Support
    The interface means the controls to use the DAM system. This is different from the metadata support which is usually entered by end users when cataloguing assets.
  • English
  • Multilingual Metadata Support
    See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
  • Yes
  • Multilingual Support Notes
    Metadata can be added in any common language

    Version Control

    File versioning
    File versioning refers to the digital media associated with an asset record. This is usually the minimum requirement for a DAM system to claim support for versioning assets. See also responses to the related question about metadata versioning below.
  • Yes
  • Metadata versioning
    Metadata versioning is separate from the files associated with assets. Many DAM solutions will track updated digital assets but only retain a single current version of the metadata. Since metadata is likely to be edited many more times than assets get replaced, this can be an important point to check.
  • No
  • Independent Metadata And File Versioning
    This questions assesses whether the solution allows versions of either the file or metadata to be reverted independently or if both are linked to a single shared version instance.
  • Yes
  • Product Screenshots

    Log in to view screenshots.

    Product Videos

    Log in to view videos.