Visokio website     Downloads     Video tutorials     KnowledgeBase  
Export: File security and export to Excel options - Visokio Forums
Export: File security and export to Excel options
  •     Mees February 20, 2012 4:00AM
    Hi guys,
    Export to Excel is possible in case a user has a paid license on Omniscope.
    When opening an iok file via Java webstart, the Viewer that opens doesn't provide the export option.
    This is normal behaviour, but it would be very useful to enable us to give users with a paid license the export functionality in the web start viewer.

    We often get this question and cannot deliver as we use webstart.

    Just sending the iok file directly would solve the problem, but then we loose control over our file. In addition we monitor the usage of webstart and we loose this as well when sending the file directly.

    Is there anything you can do to help?

    Thanks
  • 3 Comments
  •     steve February 20, 2012 4:53AM
    I'm not sure exactly what you mean by "lose control". Typical publisher concerns are:
    1. Users saving local copies which become "stale" (old data)
    2. Users sending the file on to other people
    3. Users extracting data (presumably not a concern for you, since you want to allow export to Excel)

    Be warned that simply using WebStart doesn't address any of these concerns. While it masks the source of the IOK file, it is relatively trivial to unmask the URL; e.g. the "Recent files" File menu list in the desktop-installed Omniscope will also reveal it.

    The only way you can completely address all these concerns is by owner-locking it. But this prevents CSV export, since owner-locking is a master switch or "package seal" which prevents saving or exporting.

    If you are happy to relax these concerns somewhat, your options are:
    • ServerPlus license
      A ServerPlus license empowers your WebStart clients to export to Excel (in CSV format). Regardless of whether they have a paid license. This doesn't address any of the above concerns, though.
    • Walled Gardens (addresses concern 2)
      If you have control over the license keys for your paid users, you can consider publishing using walled gardens. With walled gardens, an IOK file can be saved "within" a walled garden. Only users whose license keys are members of that walled garden can open the file. You can further restrict a license key to be a walled-garden-only key, preventing those users from saving unrestricted IOK files. But this would also prevent your users from saving ANY file (e.g. their own data) outside of the walled garden.
    • Time-limiting the IOK file (addresses concern 1)
      You can choose whether you allow stale files to be opened with a warning, or prevent opening. Note that if you don't owner-lock the file, the user will be able to disable this setting when they save a local copy.
  •     Mees February 27, 2012 6:26AM
    Hi Steve, thanks for your answer. With 'loose control' I meant 'not having control over the file anymore'. We just don't know who has it or to whom it is sent to.
  •     tjbate February 28, 2012 4:00AM
    Arjan - Unlike with spreadsheets, Omniscope file security options are intended to allow Publishers to stop worrying about who has, or can get a copy of an IOK or IOM file.

    With the appropriate combination of file security settings, we want it to be possible for Omniscope to meet the requirements of any data publishing busienss such that mere possession of a file no longer matters.
Add a Comment

Welcome!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

Categories

Tagged