http://forums.visokio.com/discussions/tagged/metadata/feed.rss Mon, 30 Oct 17 15:22:05 -0400 Tagged with metadata - Visokio Forums en-CA http://forums.visokio.com/discussion/3207/file-metadata-counting-data-manager-blocks-per-file Thu, 26 Jan 2017 04:32:21 -0500 Alexander 3207@/discussions
We are making an inventory of all our datamanager workflows. We would like to take the next step in version management, weak spots, data load etc.
One of the items we are registering is the amount of datamanager blocks, as a derivative of the workflow complexity.
How can we (except for manual counting) easily find the number of blocks in a datamanager file?
If anyone has experience in this matter, please contact me.
Thanks!]]> http://forums.visokio.com/discussion/3119/oracle-fields-description Tue, 19 Apr 2016 06:01:28 -0400 Avizua 3119@/discussions http://forums.visokio.com/discussion/2960/images-downloading-.jpg-or-other-files-from-a-list-of-urlss Mon, 22 Jun 2015 17:22:41 -0400 sherriff 2960@/discussions My question is whether there is a way to pull those files into a folder using Omniscope and then add metadata?

If the pull of the .jpg file is not possible using Omniscope, can anyone recommend any opensource code for doing this ?]]> http://forums.visokio.com/discussion/1411/idea-metadata-extraction-from-iok-filess Thu, 22 Mar 2012 06:05:04 -0400 steve 1411@/discussions
Since this discussion began, it has been partially implemented with the following architecture:

• An Omniscope Server XML action describes the request for metadata.
  This can be executed in the scheduler or watch folder, or through command-line invocation. In future we plan to update the Server/Scheduler to also provide a network-based API (perhaps HTTP/REST), and perhaps a corresponding Java API for use in a 3rd-party application, potentially in a different process or on a different server, which provides a Java facade for that network API.
  
  
• You "execute" that XML action on a licensed Omniscope Server, permissioned to access that IOK file (the IOK file must not be locked by another license).
  
  
• The metadata is returned in a publicly defined XML format. This is either written to a specified file or to the process/console output.
  

The metadata comprises the bold items in the list below, with non-bold indicating possible future additions, to be implemented depending on complexity and usefulness.

• Data structure:
  
  • Column count, row count
    
  • Field names, types, null/non-null count, min/max/mean/median/sum/std dev/range, unique values for category fields, first 100 unique values for text fields, default function, formatting etc. and formulae
    
  • Formula analysis: dependencies tree, formula structure, recalc settings
    
  • Named queries
    
  
  
• Tabs:
  
  • Names, advanced types
    
  • Titles, annotations, branding
    
  • Thumbnails (if introduced into IOK files in future), as base64-encoded data
    
  • Colour and style settings
    
  • Active filters
    
  
  
• Views:
  
  • Types, aggregations, subsets
    
  • Headers, footers
    
  • Content view's content
    
  • Some view settings
    
  • In-use fields
    
  
  
• Branding:
  
  • Cover, back and help pages
    
  • Branding/logo images, as base64-encoded data
    
  
  
• Data sources:
  
  • Referenced sources (types, summaries, file/urls)
    
  • DataManager model (block names, types, dependencies and file paths)
    
  • Edit actions repeated on refresh (e.g. ad-hoc merges)
    
  • Global auto-refresh settings
    
  
  
• Origin / other:
  
  • Creator details / version
    
  • Window size when saved, and restore option
    
  • Version compatibility requirements, if available
    
  • Viewer empowerments
    
  • File security options
    
  • Compression options, file size
    
  • Configured image sets, links & web services
    
  • Last edit/save dates
    
  • Publisher details
    
  
  

Related ideas:

• Extend the "Folder of file metadata" data source to include the more simpler information from the list, allowing you to obtain this data in IOK format for a batch of files (complete)
  
• A GUI front-end for some of the analysis, e.g. formula dependency graph, in-use / not-used fields
  
• A document containing the above information in report form
  

See also: http://forums.visokio.com/discussion/comment/3364/#Comment_3364

Please comment below.]]> http://forums.visokio.com/discussion/2033/sources-deriving-datarenaming-pdf-document-imagess Sat, 02 Mar 2013 10:40:38 -0500 sherriff 2033@/discussions
Any suggestions as to how to do this?]]>