Monday, June 26, 2017

How to Use your SharePoint Taxonomy to Organize Content in OneDrive for Business

Check out our new article on LinkedIn to learn how to use your SharePoint taxonomy to tag content that your users are storing in OneDrive for Business.  This is another great use case and justification for investing in taxonomy!

https://www.linkedin.com/pulse/how-use-your-sharepoint-taxonomy-organize-content-onedrive-mark-leher

Tuesday, June 6, 2017

The Expanded Drug Development and Manufacturing Taxonomy

We have enlarged the Drug Development Taxonomy to include the manufacturing side as well.

The development of a new drug is a process that takes a considerable amount of time.  It includes identifying a lead compound, completing the clinical trials process, and obtaining regulatory approval.  The average time it takes to develop a drug is 12 years.  Then the manufacturing process begins.

The expanded WAND Drug Development and Manufacturing Taxonomy includes terms related to the manufacturing process as well as the development side.  It is designed to provide anyone involved in the development and manufacturing of new medicines the ability to tag and organize the enormous number of documents generated during these processes.

This taxonomy provides a strong foundation of 2,475 terms and 2,128 synonyms and it can be customized to include terms specific to the drugs that are currently being, or have been, developed.

The WAND Drug Development and Manufacturing Taxonomy covers the process of bringing a new drug to market.  Higher level terms include Discovery, Development, Drug Application Types, Drug Approval, Drug Development Agreements, Research Funding Sources, and the U.S. Food and Drug Administration.

The taxonomy also includes the topics of Pre-Clinical Development, Clinical Development, all phases of the Clinical Trials, Pharmacogenomics, Pharmacovigilance, Pharmacokinetics, and Pharmacodynamics.

On the manufacturing side, higher level terms include Materials, Products, Manufacturing Processes, and Risk Management.

Use the WAND Drug Development and Manufacturing Taxonomy to better organize data and content as you navigate the path of inventing, developing, and manufacturing a safe and effective new drug.  The companion taxonomies are the WAND Manufacturing Taxonomy - an overarching taxonomy - and the WAND Packaging Taxonomy.

The WAND Drug Development and Manufacturing Taxonomy, as with all WAND Taxonomies, is available by itself or as part of the WAND Taxonomy Library Portal.

Tuesday, May 30, 2017

Next in the WAND Manufacturing Suite - the WAND Automotive Manufacturing Taxonomy


We are excited to introduce the latest taxonomy in our Manufacturing Taxonomy Suite, thWAND Automotive Manufacturing Taxonomy.  

If you are an automobile manufacturer and are already using our WAND Manufacturing Taxonomy, you can drill down even deeper with our WAND Automotive Manufacturing Taxonomy. 

This taxonomy is designed to provide terms specific to automotive manufacturing and provides a foundation of 865 terms and 480 synonyms that can also be customized.


Top level terms include Vehicle Classifications, Assembly, Design, Performance, and Components.  National Highway Traffic Safety Administration Safety Standards, Investigations, and Recalls are also covered.

The Features category provides terms that make a car special - the Infotainment Systems, the Trim Packages, Climate Control Systems, Ergonomics, and the Instrument Panel.
As with all WAND Taxonomies, the WAND Automotive Manufacturing Taxonomy is available by itself or as part of the WAND Taxonomy Library Portal.

Tuesday, May 23, 2017

Announcing the WAND Packaging Taxonomy.

The latest taxonomy in our Manufacturing Taxonomy Suite is the WAND Packaging Taxonomy.  This taxonomy provides a foundation of 525 terms and 148 synonyms and was designed for any company packaging items for consumers, for transporting, or for warehousing.

This is a perfect companion taxonomy to both the WAND Manufacturing Taxonomy and the WAND Food and Beverage Manufacturing Taxonomy.

Top level terms include Labeling, Product Packaging, Packaging Supplies and Containers.

Packaging Machinery, Packaging Testing, the Fair Packaging and Labeling Act, and Packaging Test Standards are also top level terms.

As with all WAND Taxonomies, the WAND Packaging Taxonomy is available by itself or as part of the WAND Taxonomy Library Portal.

Tuesday, May 16, 2017

Next in the WAND Manufacturing Suite - the WAND Food and Beverage Manufacturing Taxonomy


We are excited to introduce the latest taxonomy in our Manufacturing Taxonomy Suite, the WAND Food and Beverage Manufacturing Taxonomy

If you are a food or beverage manufacturer and are already using our WAND Manufacturing Taxonomy, you can drill down even deeper with our WAND Food and Beverage Manufacturing Taxonomy. 

This taxonomy is designed to provide terms specific to food and beverage manufacturers and provides a foundation of 1,148 terms and 232 synonyms that can also be customized.

This taxonomy includes terms relating to all aspects of Food Labeling including the individual Food Label Panels and Formats.  

Food Production, Food Products, Recalls, and Hazards are top level terms along with Regulatory Agencies, Food Manufacturing Laws, Food Guidance and Regulations, Standards, and Associations. 
Watch for our soon-to-be released WAND Packaging Taxonomy which will address the terms associated with the packaging process.

As with all WAND Taxonomies, the WAND Food and Beverage Manufacturing Taxonomy is available by itself or as part of the WAND Taxonomy Library Portal.

Tuesday, April 4, 2017

The WAND Manufacturing Taxonomy has been expanded!

The WAND Manufacturing Taxonomy has been expanded.  It provides a foundation of 1,170 terms and 371 synonyms and can be customized to include specific terms to meet the document management needs of any manufacturing company. 

In this expansion we've added to several areas. The Manufacturing Planning section has been changed to include Scheduling.  Manufacturing Production now incorporates Methods, Strategies, Production Processes, Production Control, and more.  Manufacturing Safety has also been expanded.

We have added both Documents and Records as well as Guidelines and Regulations as top level terms.

Manufacturing Processes is a new top level term.  It includes Discrete Manufacturing, Process Manufacturing, and Additive Manufacturing.

Discrete Manufacturing covers Bill of Materials and Process Manufacturing contains Formulations and Ingredients.  Additive Manufacturing (3D Printing) incorporates terms relating to Additive Manufacturing Techniques, Scanning, Process Types, and Materials - both Filaments and Powder Additives.

To focus on specific areas of manufacturing we will soon be releasing several new taxonomies to complement our WAND Manufacturing Taxonomy.  The first of these will be the new WAND Food and Beverage Manufacturing Taxonomy and the WAND Packaging Taxonomy.
As with all WAND Taxonomies, the WAND Manufacturing Taxonomy is available by itself or as part of the WAND Taxonomy Library Portal.

Wednesday, March 22, 2017

Why the SharePoint Managed Metadata Service and Term Store should be standalone Office Applications.

Microsoft has been progressive in supporting taxonomy and metadata in SharePoint.  The Managed Metadata Service was first released as part of SharePoint 2010 and was a dramatic improvement over existing metadata capabilities.  For the first time, companies could deploy defined hierarchies of terms with which to tag, filter, and search content.  Today, the Managed Metadata Service continues as part of SharePoint 2013, SharePoint 2016 and SharePoint Online. Taxonomy and structured metadata add tremendous value in many Microsoft applications including SharePoint, OneDrive, Delve, Microsoft Teams, Yammer, and Flow.

(See earlier blog posts "Taxonomy: The Missing Signal in Microsoft Delve" and "Why Microsoft Teams Must include support for Managed Metadata and Taxonomy").

Has the time come where Managed Metadata has outgrown SharePoint?  I'd say yes - it's time for Microsoft to break out the Managed Metadata Service and make it a standalone Office application.

A standalone Managed Metadata Service would enable powerful features across the Office Suite 


Separating the Managed Metadata Service from SharePoint would increase the prominence of metadata and taxonomy and make it clear how important metadata is for organizing enterprise information.   Separating it would also open the door to do specific metadata integrations with other applications besides SharePoint.

Office 365 is an ecosystem of valuable productivity and collaboration applications.  Managed Metadata and taxonomy can be a common thread woven throughout the ecosystem.

For example, an Excel drop down list could be powered by a Term Set in the standalone Managed Metadata Service.  This would allow for consistent pick lists across various sheets (and values picked from this list could be leveraged as a signal in Delve - see earlier post with my suggestions for that)

Many WAND customers who are developing an enterprise taxonomy are worried about how they will enforce tagging.  Currently the choice is between just manual tagging upon check-in and investing in a third party automatic tagging engine.  There is a middle way, I believe.   The middle way is a tag suggest feature - I'll call it "Intelligent Tag Suggest".   A user creating a Word document could type a term in the body of the document that also appears in the Term Store.  Word could then prompt the user that this occurred and ask them if they would like to tag the document with the term.   Term descriptions and alternate descriptions could be used to power this "Intelligent Tag Suggest" feature, and the Term Store could be enhanced to allow softer clue terms to be added to each taxonomy concept.  "Suggest as Tag" could be a configurable option for each Term Set or each individual term.

Microsoft is starting to recreate taxonomy management capabilities elsewhere.


Last year, Microsoft released the Azure Data Catalog to general availability.  Azure Data Catalog  has a Business Glossary feature which replicates many of the features of the Term Store (Read more about Azure Data Catalog at  https://docs.microsoft.com/en-us/azure/data-catalog/data-catalog-how-to-business-glossary).

A single Microsoft application that could manage vocabularies across applications makes more sense and would encourage the appropriate re-use of vocabularies across an organization.

Expand the capabilities of the Term Store to make it a more complete taxonomy solution


A few basic features I would advocate for a standalone Term Store would include:

  1. Add support for relationship types between concepts besides Broader Term/Narrower Term   
  2. Ontology and taxonomy auditing and governance features - expand the foundation in place with Term Groups.
  3. Connections where appropriate to individual Office applications and settings to support taxonomy within those applications. 
  4. Improved import and export support, including support for common XML formats, advanced relationship types, and synonyms.
  5. Metadata Graph: help admins visualize where various concepts and terms sets from the term store are used across the enterprise.  This is something that could be added just in SharePoint to add a huge amount of value and help admins map out their metadata models.

A standalone Managed Metadata Service would be a strategic advantage for Microsoft


Besides adding tremendous value to users, a standalone term store with more robust taxonomy and ontology management capabilities would be a huge strategic differentiation and put Microsoft in the driver's seat for expanding its footprint within existing clients.  Simply put, taxonomy is a foundation component to a wide variety of enterprise applications.

Taxonomy is sticky.  The more deeply taxonomy and Managed Metadata is integrated within the complete Office Suite, the more entrenched Microsoft will be inside an organization.  There is no other enterprise software provider with the level of support for taxonomy that Microsoft already has in SharePoint.  Companies which have invested in taxonomy won't readily be able to duplicate this if they try to migrate out of Office 365.  Any other metadata fields can generally be handled elsewhere but Managed Metadata cannot easily be migrated.

Taxonomy support can and should extend outside of the core Office suite of applications.  Business intelligence, big data analytics, search, and ERP applications (Accounting - account ledger categories; Procurement - spend analysis categories and buyer catalog), data catalogs, etc all significantly benefit from taxonomy.   With a standalone Managed Metadata Service, users would naturally come to Microsoft's suite of applications because taxonomy would be ready to go.  Internal Microsoft development across its suite would no longer need to re-build the wheel and could simply hook into the standalone Managed Metadata Service for each application.

Microsoft should devote resources to adding features to the term store to transform it from a taxonomy management environment to a complete taxonomy and ontology management tool. This investment would drive metadata and tagging throughout and beyond the Office Suite and would facilitate taxonomy re-use for Microsoft's clients.    

If you agree, please vote on Microsoft User Voice to let Microsoft know that you think this is an important idea. 

Vote at https://office365.uservoice.com/forums/264636-general/suggestions/18691123-the-sharepoint-term-store-should-be-a-standalone-o