5. GOALS
• Why are we going to talk about metadata?
• Improve navigation
• Improve findability
(fact that we find what we’re looking for)
• Improve discoverability
(fact that we find what we’re not looking for)
• Improve user experience
• Allow to build a governance strategy
• Save money/add value for the company
10. METADATA ARE DEFINED BY THEIR
FUNCTION
• Ease search/discovery of
information
• Describe content and
relationships between files
• Classify content based on
targeted audience
• Help the SEO of a page
• Ease the interoperability
• Share information
• Ease management and
archiving
• Give an information about the
document’s lifecycle
• Manage sets of resources
• Manage electronic archives
• Manage rights
• Copyright
• Security
11. METADATA TYPES
• Bibliographic Metadata: allowing to access the document
(author, title, creation date, modification date…)
• Administrative Metadata: legal, lifecycle, copyright,
processing
• Technical Metadata: format, how it was produced, storage.
• Description Metadata: to understand the content
12. DUBLIN CORE
Dublin core elements
Title Given name of the resource
Author Entity mainly responsible for resource’s content creation.
Subject Subject of the content (controlled vocabulary and classification schemas are suggested)
Description Description of the content (eg. Summary, table of content, or simply text…)
Editor Entity responsible for resource’s diffusion (company, university…)
Contributor Entity which contributed to the creation of the content.
Date Date associated to an event in resource’s lifecycle (format : see ISO 8601)
Type
Nature ou genre (ex. categories, functions, general kind… controlled vocabulary recommended, see Dublin
Core)
Format Physical or digital materialization of the content (mime-type)
Identifier Disambiguated (unique) reference to the content (examples : URI, URL, DOI, ISBN)
Source Reference to a resource from which this one has been derived.
Language Content’s language
Relation Reference to another related resource.
Coverage Range or coverage of the resource in space or time or legally.
Rights Security and copyright information.
14. CONTROLLED VOCABULARY
• A controlled vocabulary is a glossary designed to
allow knowledge organization in order to optimize
information lookup/search.
• Classification schemes (taxonomy, thesaurus,
ontology) use a controlled vocabulary.
15. TAXONOMY
• Subsumption relationship “is-a”
• Transitivity
• If C is a B and B is an A, C is an A
Vehicules
Land
Vehicules
Car
Truck
Bus
Air
Vehicules
Airplane
Balloon
Rocket
Sea
Vehicule
Boat
Submarine
16. THESAURUS
• Taxonomy++
• Hierarchy + properties
Conept or potential term Car
Generic Term Véhicule
Specific Term
Domains vehicule - transport [MT 3330]
Regional variations
French equivalent voiture
Associated Terms [TA] craft : transport [MT 6005]
automobile technic [MT 3510]
19. FOLKSONOMY
• Comes from “folk” (people) and “taxonomy”. Indexing
spontaneously by keywords without pre-defined
classification.
• This process is collaborative. (sometimes also called social
tagging)
20. FACETS
• Description of a resource following multiple
axes
• Allows you to search/refine by facet
21. CONCEPTS
• Term = denomination + concept
• Denomination = linguistic expression
• Concept = meaning
• The term has to have a context to understand the concept
• Ex table
• Coffee table?
• Table of content?
• Timetable?
• Discussion table?
22. NAMED ENTITIES
•Main types of entities
•Person’s names
•Places
•Organizations
•Products
•Dates
•Currencies
23. RECAP
Schema Taxonomy Thesaurus Ontology Folksonomy Facets
Organization
Simple
hierarchical
relationships
Hierarchical
relationships
(hyponymy,
hypernymy) ,
associative
relationships
and equivalent
relationships
Concepts with
types,
properties and
relationships
Tags set by users
as the like
Allows to
describe a
resource
following
multiple azes
Relationship
type
« is a » « is a »
« sort of »
« related to »
« synonym »
« equivalent »
« contains »
« is located»
« uses »
« produces »
« … »
« price »
« product »
« kind »
Context Library Web 3.0 Web 2.0
Example Dewey Rameau Cyc, Wordnet Flickr, YouTube Amazon
26. FOLDERS
• A folder structure is already a form of metadata
•Very simple to set up
• Complicated to change
• Trick
• Don’t use it unless you have permissions related
needs
27. TAXONOMY
•Advantages:
• Search
• Filtering
• Advanced control
• Consistency
•Disadvantages:
• Takes time to set up
•Tips:
• Use most issued search
requests to improve it!
• Delegate management of
some branches
• If you don’t have a clear
idea yet, use folksonomy
28. ENTERPRISE KEYWORDS
• Advantages:
• Easier fro end users
• Takes into consideration keywords inside of
documents
• Disadvantages:
• Harder to manage
• No context during indexation
29. FOLKSONOMY
Content « like »
Tagging (with user’s words)
Notes
User Profile
Filtered Navigation
Search refiner
Topics and power users to follow
Deprecated on SharePoint online!!!
30. DOCUMENTS SETS
« this document is related to that other one »
Creates a documents « group » model
Properties can be common or individual
Trick:
Can also be used for security purposes (not primary
role)
Don’t hesitate to create new content types inhereting
from it
31. COLUMNS AND CONTENT TYPES
• Information about what the content is (CT)
• Adds properties (columns)
• Allows filtering, refinement, search….
• Allows to have multiple entry forms(CT)
32. NAVIGATION BY TAXONOMY
• Enhances nvigation
• Prepares users to use refiners
• Easy to set up
• Is a great alternative to/transition from folders
33. WIKIS
• Quick pages creation system
• Allows to link web content
• Advantages:
• Very easy and fast to set up
• Disadvantages:
• No advanced publication features
34. SEO/WEB METADATA
• By default SharePoint pages include little metadata (search
engines)
• Publishing + 2013 allows us to provide more data
• Description
• Keywords
• Sitemap
• Author
• Browser title
• …
35. FACETS
• Improve search
• Located on the left with search results
• Use metadata (all)
• You can (must!) customize it
• Very efficient to filter out not relevant data and drill down
to the right result
36. DOCUMENT CENTER
• Organizes content with taxonomy
• Drop off library
• Applies governance rules based on taxonomy
37. SITE METADATA NAVIGATION
•Build top navigation + urls with
taxonomy
•Useful for SEO
•Great to build a portal in a “semantic”
way
•Structure depends on your thesaurus
38. OTHER METADATA
• Author
• Security
• Views (count)
• Containers (sites, doc libs…)
• Resource type (extension, mime)
• Dates (creation, modification…)
• Status (approval)
42. WHAT’S THE POINT?
The general idea is to have a
precise representation and a good
structure of the ideas of the
company
Copyright Vincent BIRET ;-)
43. YES BUT!
Users never fill up metadata!
Solutions:
Index their salary on metadata fill up rate
Wall of shame of worst metadata “filler” of the company
Automate that part!
45. GRAPH
• First of all it’s a mathematics model
• Nodes, edges and by transivity “routes”
• Then data model
• Idea that on piece of data is related to another
• Finally Microsoft is making huge investments for
businesses
• Actors, signals, objects
• Schema is extensible to add METDATA!
48. WHAT’S THE IDEA?
• Pro-active content
• Discoverability
• No need to search for something anymore
• If we still need to search something, way more efficient
• Make you save time, therefor money
50. CONCLUSION
•We improved navigation
•We improved findability
•We improved discoverability
•We improved user experience
•Everybody saves time
•The company saves money
51. THANK YOU
EVENT SPONSORS
We appreciated you supporting the New York SharePoint Community!
• Diamond, Platinum, Gold, & Silver have tables scattered throughout
• Please visit them and inquire about their products & services
• To be eligible for prizes make sure to get your bingo card stamped by ALL sponsor
From greek « meta » which means talking about itslef, autoinference and data. Metadata are data about data!
It can be as much diverse as associated copyright, GPS data, likes…
Name coming from a focus group united in 1995 in dublin, ohio. Goal: define a common set of elements that the us gov could use. Dublin core is a simple generic descriptive format with 15 elements. Other standards exist (ISO)
Origines Carl von linné (XVII century) developed a classification system for living organisms.
Ontology is a formal language, a grammar that defines the concepts of a domain, their properties and their relationships
The information can be a like, a comment, a tag, a mention, a hashtag…
Origin: "colon classification" (shiyali Ramamrita Ranganathan, 1933) with 5 basic categories of description or faceted to characterize any document or application question: Personality, Matter, Energy, Space, Time Ex: The woolen gloves manufacturing theme Bradford in the 19th century is described by Personality gloves = / = Material wool / Energy production = / = Location Bradford / time = 19
Concepts are the representation of an idea
Named entities are language elements referring to a unique and concreate entity belonging to a specific domain (humain, geographic, economic…)
Goal: understand what’s sharepoint able to do
https://support.office.com/en-ie/article/Introduction-to-managed-metadata-a180fa28-6405-4679-9ec3-81d2028c4efc
Great whitepaper
http://blogs.technet.com/b/tothesharepoint/archive/2013/10/24/search-engine-optimization-seo-in-sharepoint-server-2013.aspx
Search is inefficient, so we gather metrics. We try to organize ideas so we build a thesaurus.
Once we have that let’s update data. Which will allow us to have a better navigation structure.
So the need for search decreases. The structure will also allow us to define a governance plan and archive obsolete data, hence improving search results… and so on