Tag Archives: DAM

Using Google to Search Personal Data: Calendar, Gmail, Photos, and …

On June 16th, 2017,  post reviewed for relevant updates.

Reported by the Verge,  Google adds new Personal tab to search results to show Gmail and Photos content on May 26th.

Google seems to be rolling out a new feature in search results that adds a “Personal” tab to show content from [personal] private sources, like your Gmail account and Google Photos library. The addition of the tab was first reported by Search Engine Roundtable, which spotted the change earlier today.

I’ve been very vocal about a Google Federated Search, specifically across the user’s data sources, such as Gmail, Calendar, and Keep. Although, it doesn’t seem that Google has implemented Federated Search across all user, Google data sources yet, they’ve picked a few data sources, and started up the mountain.

It seems Google is rolling out this capability iteratively,  and as with Agile/Scrum, it’s to get user feedback, and take slices of deliverables.

Search Roundtable online news didn’t seem to indicate Google has publicly announced this effort, and is perhaps waiting for more sustenance, and more stick time.

As initially reported by Search Engine Roundtable,  the output of Gmail results appear in a single column text output with links to the content, in this case email.

Google Personal Results
Google Personal Search Results –  Gmail

It appears the sequence of the “Personal Search” output:

  • Agenda (Calendar)
  • Photos
  • Gmail

Each of the three app data sources displayed on the “Personal” search enables the user to drill down into the records displayed, e.g.specific email displayed.

Google Personal Search Calendar
Google Personal Search Results –  Calendar

 Group Permissions – Searching

Providing users the ability to search across varied Google repositories (shared calendars, photos, etc.) will enable both business teams, and families ( e.g. Apple’s family iCloud share) to collaborate and share more seamlessly.  At present Cloud Search part of G Suite by Google Cloud offers search across team/org digital assets:

Use the power of Google to search across your company’s content in G Suite. From Gmail and Drive to Docs, Sheets, Slides, Calendar, and more, Google Cloud Search answers your questions and delivers relevant suggestions to help you throughout the day.

 

Learn More? Google Help

Click here  to learn more on, “Search results from your Google products”  At this time, according to this Google post:

You can search for information from other Google products like Gmail, Google Calendar, and Google+.


Dear Google [Search]  Product Owner,

I request Google Docs and Google Keep be in the next data sources to be enabled for the Personal search tab.

Best Regards,

Ian

 

AI Email Workflows Eliminate Need for Manual Email Responses

When i read the article “How to use Gmail templates to answer emails faster.”  I thought wow, what an 1990s throwback!

Microsoft Outlook has had an AI Email Rules Engine for years and years. From using a simple Wizard to an advanced construction rules user interface. Oh the things you can do. Based on a wide away of ‘out of the box’ identifiers to highly customizable conditions, MS Outlook may take action on the client side of the email transaction or on the server side. What types of actions? All kinds of transactions ranging from ‘out of the box’ to a high degree of customization. And yes, Outlook (in conjunction with MS Exchange) may be identified as a digital asset management (DAM) tool.

Email comes into an inbox, based on “from”, “subject”, contents of email, and a long list of attributes, MS Outlook [optionally with MS Exchange], for example, may push the Email and any attached content, to a server folder, perhaps to Amazon AWS S3, or as simple as an MS Exchange folder.

Then, optionally a ‘backend’ workflow may be triggered, for example, with the use of Microsoft Flow. Where you go from there has almost infinite potential.

Analogously, Google Gmail’s new Inbox UI uses categorization based on ‘some set’ of rules is not something new to the industry, but now Google has the ability. For example, “Group By” through Google’s new Inbox, could be a huge timesaver. Enabling the user to perform actions across predefined email categories, such as delete all “promotional” emails, could be extremely successful. However, I’ve not yet seen the AI rules that identify particular emails as “promotional” verses “financial”. Google is implying these ‘out of the box’ email categories, and the way users interact, take action, are extremely similar per category.

Google may continue to follow in the footsteps of Microsoft, possibly adding the initiation of workflows based on predetermined criteria. Maybe Google will expose its AI (Email) Rules Engine for users to customize their workflows, just as Microsoft did so many years ago.

Although Microsoft’s Outlook (and Exchange) may have been seen as a Digital Asset Management (DAM) tool in the past, the user’s email Inbox folder size could have been identified as one of the few sole inhibitors.  Workaround, of course, using service accounts with vastly higher folder quota / size.

My opinions do not reflect that of my employer.

Applying Gmail Labels Across All Google Assets: Docs, Photos, Contacts + Dashboard, Portal View

Google applications contain [types of] assets,  either created within the application, or imported into the application.    In Gmail, you have objects, emails, and Gmail enables users to add metadata to the email in the form of tags or “Labels”.  Labeling emails is a very easy way to organize these assets, emails.   If you’re a bit more organized, you may even devise a logical taxonomy to classify your emails.

An email can also be put into a folder and this is completely different than what we are talking about with labels.  An email may be placed into a folder, and have a parent child folder hierarchy.  Only the name of the folder, and it’s correlations to positions in the hierarchy provide this relational metadata.

For personal use, or for small to medium size businesses, users may want to categorize  all of the Google “objects” from each Google App,  so why Isn’t there the capability to apply labels across all Google App assets?  If you work at a law firm, for example, and have documents in Google Docs, and use Google for email, it would be ideal to leverage a company wide taxonomy, and upon any internal search discover all objects logically grouped in a container by labels.

For each Google object asset, such as email in Gmail, users may apply N number of labels to each Google Object asset.

A [Google] dashboard, or portal view may be used to display and access Google assets across Google applications, grouped by Labels .  A Google Apps “Portal Search” may consist of queries that contain asset labels.  A  relational, Google object repository containing assets across all object types (e.g. Google Docs), may be leveraged to store metadata about each Google asset and their relationships.

A [Google] dashboard, or portal view may be organized around individuals (e.g. personal), teams, or an organization.  So, in a law firm, for example, a case number label could be applied to Google Docs,  Google Photos (i.e. Photos and Videos),  and of course, Gmail.

A relatively simple feature to be implemented with a lot of value for Google’s clients, us?  So, why isn’t it implemented?

One better, when we have facial recognition code implemented in Photos (and Videos), applying Google labels to media assets may allow for correlation of Emails to Photos with a rule based engine.

The Google Search has expanded into the mobile Google app.

Leveraging Google “Cards“, developers may create “Cards” for a single or group of Google assets.   Grouping of Google assets may be applied using “Labels”.   As Google assets go through a business or personal user workflow, additional metadata may be added to the asset, such as additional “Labels”.

Expanding upon this solution,  scripts may be created to “push” assets through a workflow, perhaps using Google Cloud Functions.  Google “Cards” may be leveraged as “the bit” that informs users when they have new items to process in a workflow.

Metadata, or Labels, may be used such as “Document Ready for Legal Review” or “Legal Document Review Completed”.

Human Evolution: Technology Continues to Transform Socieities for Generations

In the last 20 years, I’ve observed technology trends, and Tech achievements have risen and fallen from the mainstream.  Tech has augmented our lives, and enhanced our human capabilities.  Our evolution will continue to be molded by technology and shape humanity for years to come.

Digital Asset Management (DAM)

Everything you might find on your computer from emails to video are digital assets.  Content from providers, team collaboration,  push and/or pull asset distribution, and archiving content are the workflows of DAM.

DAM solutions are rapidly going main stream as small to medium sized content providers look to take control of their content from ingestion to distribution.  Shared digital assets will continue to grow rapidly.  Pressure by stockholders to maximize use of digital assets to grow revenue will fuel initiatives to  globally share and maintain digital asset taxonomies.  For example, object recognition applied to image, sound and video assets will dynamically add tags to assets in an effort to index ever growing content.  If standard taxonomies are not globally adopted, and continually applied to assets, digital content stored will become, in essence, unusable.

The Internet of Things (IoT)

All devices across all business verticals will become ‘Smart’ devices with bidirectional data flow.  Outbound ‘Smart’ device data flow is funneled into repositories for analysis to produce dashboards, reporting, and rules suggestions.

Inbound ‘Smart’ device data can trigger actions on the device. Several devices may work in concert defined by ‘grouping’ e.g. Home: Environmental. Remote programming updates may be triggered by the analysis of data.

  • AI Rules Engine runs on ‘backend’.  Rules defined by Induction,  through data analysis, and human set parameters,  executed in sequence
  • Device optimization updates, presets on devices may be tuned based on ‘transaction’ history, feedback from user, and other ‘Smart’ devices.
  • Grouped ‘Smart’ devices, e.g. health monitors’ data uploaded, analyzed, and correlating across group.  Updated rules, and notifications triggered.
  • Manual user commands, ad hoc or scheduled

… as a Service

Cloud ‘Services’ enables scalability on demand, relatively lower cost [CapEx] overhead, offsite redundancy, etc.  Provides software solutions companies to rapidly deploy to Dev., Test, and Prod. environments.  Gaming, storage, and virtual machines are just a few of the ‘…as a service’ offerings.  IoT analysis may reveal a new need for another service.

Human Interface

  • Augmented Reality A.R.

Integrates user to surrounding environment with overlay images to your eyes to REpresent anything, e.g. Identifies surrounding people with Twitter handle/user name above their heads.  Interacts with smartphone for Inbound and outbound data flow.  May allow App and OS programmers to enable users to interact with their ‘traditional’ software in new ways, e,g. Microsoft Windows 8+, current interaction with ’tiles’, may shift from a two to three dimensional manipulation and view of the tiles.  Tiles (apps) pop up when, through object recognition, predefined characteristics match, e.g.  Looking at a bank check sent to you from the mail?  Your Bank of America tile / app may ask if you want to deposit the check right now?

  • Virtual Reality, V.R.

As more drones, for example, collect video footage, may be used for people to experience the landscapes, beaches, cities, mountains, and other features of a potential destination, which may lead to tourism.  In fact, travel agencies may purchase the V.R. Headsets, and subscribe to a library of V.R. content.  Repository platform would need to be created.  Specs for the ‘How To’ on collecting V.R. Video footage should be accessible.  Hathaway real estate offers a V.R. tour of the house, from their office.

Autonomous  Vehicles (Average Consumer or hobbyist)

  • Cars 
  • Drones
  • Satellites 

Social Media Evolution

Driving forces to integrate with society puts pressure on individuals to integrate with the collective social conscious.  As digital assets are published, people will lunge at the opportunity to self tag every digital asset both self and community shared assets.  Tagging on social media platforms is already going ahead.   Taxonomies are built, maintained and shared across social media platforms.  Systematically tagged [inanimate] objects occur using object recognition. Shared, and maintained global taxonomies not only store data on people and their associated meta data, (e,g,  shoe size, education level completed, HS photo,etc.) but also store meta data about groups of people, relationships and their tagged object data.

The taxonomies are analyzed and correlated, providing better, more concise demographic profiles.  These profiles can be used for 

  • Clinical trials data collection
  • Fast identification of potential outbreaks, used by the CDC
  • The creation and management of AI produced Hedge Funds
  • Solicitation of goods and services

Out of Compliance

These three dreaded words you are guaranteed to see more and more often.  As all aspects of our lives become meta data on a taxonomy tree, the analysis of information will make correlations which drive consumers and members of society ‘out of compliance’.  For example, pointers to your shared videos of you skydiving will get added to your personal taxonomy tree.  Your taxonomy tree will be available and mandatory to get life insurance from a tier 1 company.  Upon daily inspection of your tree by an insurance AI engine, a hazardous event was flagged. Notifications from your life insurance company reminding you ‘dangerous’ activities are not covered on your policy.  Two infractions may drive up your premiums.

Google Introduces their Cloud, Digital Asset Management (DAM) solution

Although this is a saturated space, with many products, some highly recommended, I thought this idea might interest those involved in the Digital Asset Management space.  Based on the maturity of existing products, and cost, it’s up to you, build or buy.  The following may provide an opportunity for augmenting existing Google products, and overlaying a custom solution.

Google products can be integrated across their suite of solutions and may produce a cloud based, secure, Digital Asset Management, DAM solution.   In this use case, the digital assets are Media (e.g. videos, still images)

A Google DAM may be created by leveraging existing features of Google Plus, Google Drive, YouTube, and other Google products, as well as building / extending additional functionality, e.g. Google Plus API, to create a DAM solution.   An over arching custom framework weaves these products together to act as the DAM.

Google Digital Asset Management (New)

  1. A dashboard for Digital Asset Management should be created, which articulates, at a glance, where project media assets are in their life cycle, e.g. ingestion, transcoding, editing media, adding meta data, inclusion / editing of closed captions, workflow approvals, etc.
  2. Creation and maintenance of project asset folder structure within storage such as Google Drive for active projects as well as Google Cloud Storage for archived content.  Ingested content to arrive in the project folders.
  3. Ability to use [Google YouTube] default encoding / transcoding functionality, or optionally leverage alternate cloud accessible transcoding solutions.
  4. A basic DAM UI may provide user interaction with the project and asset meta data.
  5. Components of the DAM should allow plug in integration with other components on the  market today, such as an ingestion solution.

Google Drive and Google Cloud Storage.  Cloud storage offers large quantities of storage e.g. for Media (video, audio), economically.

  1. Google Drive ingestion of assets may occur through an automated process, such as a drop folder within an FTP site.  The folder may be polled every N seconds by the Google DAM orchestration, or other 3rd party orchestration product, and ingested into Google Drive.  The ingested files are placed into a project folder designated by the accompanying XML meta file.
  2. The version control of assets, implemented by Google Drive and the DAM to facilitate collaboration and approval.
  3. Distribution and publishing media to designated people and locations, such as to social media channels, may be automatically triggered by DAM orchestration polling Google Drive custom meta data changes.   On demand publishing is also achievable through the DAM.
  4. Archiving project assets to custom locations, such as Google Cloud solution, may be triggered by a project meta data status modification, or on demand through the DAM.
  5. Assets may be spawned into other assets, such as clips.  Derived child assets are correlated with the master, or parent asset within the DAM asset meta data to trace back to origin.  Eliminates redundancy of asset, enabling users to easily find related files and reuse all or a portion of the asset.

Google Docs

  1. Documents required to accompany each media project, such as production guidelines, may go through several iterations before they are complete.  Many of the components of a document may be static.  Google Docs may incorporate ‘Document Assembly’ technology for automation of document construction.

Google’s YouTube

  1. Editing media either using default YouTube functionality, or using third party software, e.g. Adobe suite
  2. Enable caption creation and editing  may use YouTube or third party software.
  3. The addition & modification of meta data according to the corporate taxonomy may be added or modified through [custom] YouTube fields, or directly through the Google DAM Db where the project data resides.

Google’s Google Plus +

  1. G+ project page may be used for project and asset collaboration
  2. Project team members may subscribe to the project page to receive notifications on changes, such as new sub clips
  3. Asset workflow notifications,  human and automated:
    1. Asset modification approvals (i.e. G+ API <- -> DAM Db) through custom fields in G + page
    2. Changes to assets (i.e. collaboration) notifications,
    3. [Automated] e.g. ingestion in progress, or completed updates.
    4. [Automated] Process notifications: e.g. ‘distribution to XYZ’ and ‘transcoding N workflow’.  G + may include links to assets.
  4. Google Plus for in-house, and outside org. team(s) collaboration
  5. G + UI may trigger actions, such as ingestion e.g.  by specifying a specific Google Drive link, and a configured workflow.

Google Custom Search

  1. Allows for the search of assets within a project, within all projects within a silo of business, and across entire organization of assets.
  2. Ability to find and share DAM motion pictures, still images, and text assets with individuals, groups, project teams in or outside the organization.  Google Plus to facilitate sharing.
  3. Asset meta data will e.g. describe how the assets may be used for distribution, digital distribution rights.   Users and groups are implemented within G+, control of asset distribution may be implemented in Google Plus, and/or custom Google Search.

Here are a list of DAM vendors.