Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
•Télécharger en tant que PPTX, PDF•
22 j'aime•30,836 vues
Metadata provides a foundation for the cross-channel experiences we consume in the dawn of the 21st century by enabling consistency, context and interoperability. While Metadata is key to many of the User Experience methods we use – from triggering Content Strategy workflows to enabling faceted search through groups, sorts and filters, it remains a mystery to many of us. This session is a crash course on Metadata in the 21st century for UX Designers. We'll look at recent developments in the field, and build an understanding of how Metadata enables the exchange of information between parties, channels, systems and platforms through semantic, syntax and lexical specifications. Attendees will understand how Metadata fits into UX methods and tools they already know – using an ontology to support a mental model for example. This session is a must for all UX Designers looking to build meaningful cross-channel experiences in an increasingly interlinked world.
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
Similaire à Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012 (20)
Plus de aungstad
Plus de aungstad (7)
Dernier
Dernier (20)
Better Cross-Channel Experiences With Metadata - Information Architecture Summit 2012
- 1. Better Cross-Channel Experiences With Metadata @AdamUngstad #XChannelMetadata
- 3. consistency
- 4. context
- 10. information about information objects
- 11. the content
- 12. the containers
- 14. what is an information object?
- 17. Document
- 19. 3 Types of Metadata
- 21. Descriptive
- 26. When used with UX techniques such as
- 27. Faceted Search
- 30. Administrative
- 31. manage
- 32. Status Expiry Date Content Owner Access Rights Intellectual Property
- 34. Right content Right time Right channel Right user
- 35. When used with UX techniques such as
- 36. Content Strategy
- 39. Structural
- 41. Name
- 42. First Name Middle Initial Last Name
- 43. First Name Other Given Names cv cv Surname Surname (Birth) cv Surname (Previous) cv
- 44. When used with UX techniques such as
- 45. Form Design
- 47. Channels
- 48. Multi-Channel
- 49. Website SMS Mail In-Store Phone
- 50. Website SMS Mail In-Store Phone
- 51. Website SMS Mail In-Store Phone
- 52. Cross-Channel
- 53. Website SMS Mail In-Store Phone
- 54. Website SMS Mail In-Store Phone
- 57. So how do we exchange information?
- 58. 3 Sides of Information Architecture
- 59. Presentation
- 61. Storage
- 63. Exchanges
- 64. Exchanges
- 65. each side has a unique structure
- 66. exchanges
- 68. X
- 69. X Y
- 70. X Y Z
- 71. Z
- 72. Z Org 1 Org 4 Org 2 Org 3
- 73. What is ‘Z’?
- 75. RDF Z Org 1 Org 4 Org 2 Org 3
- 76. Z NIEM Org 1 Org 4 Org 2 Org 3
- 77. DUBLIN Z CORE Org 1 Org 4 Org 2 Org 3
- 78. Good Z Relations Org 1 Org 4 Org 2 Org 3
- 79. Z OASIS Org 1 Org 4 Org 2 Org 3
- 80. XML Z Org 1 Org 4 Org 2 Org 3
- 84. what is defined by a metadata standard?
- 85. Semantics
- 86. meaning
- 87. “bench”
- 90. Syntax
- 91. expression
- 92. capsicum
- 93. pepper
- 94. Name
- 95. 3ric?
- 96. St. Germaine?
- 97. Lexical Rules
- 98. words
- 99. Name
- 100. The Cookie Monster?
- 101. Talula Does The Hula From Hawaii?
- 103. Experiences
- 105. If a pepper is an information object...
- 106. ...a user is one too.
- 107. Website SMS Mail In-Store Phone
- 108. is an experience ‘one size fits all’?
- 110. experiences must be personalized
- 111. previous experiences
- 112. memories
- 113. expectations
- 114. wants
- 115. interests
- 116. aspirations
- 117. behaviours
- 118. each channel
- 119. must know the user
- 120. users are not an exchange mechanism!
- 121. X Y Z
- 122. never ask for something twice
- 123. you only get one first chance
- 124. What to do on Monday:
- 125. 1. make metadata a priority
- 126. link metadata to ROI
- 128. create loyalty
- 129. 2. define your data
- 130. information objects
- 131. content assets
- 132. users
- 133. relationships
- 134. 1:1 1 : many many : many
- 135. 1:1 1 : many many : many
- 136. is part of is delivered by is used with
- 137. Ontology
- 139. Mental Models
- 141. Contextual Inquiries
- 142. Diary Studies
- 143. discover what needs to be defined
- 144. specify
- 145. semantics syntax lexical rules
- 146. start with a controlled vocabulary
- 148. internal & external
- 149. Journey Map
- 150. @uxjam
- 151. Business Origami
- 152. @jessmcmullin
- 153. happy paths
- 154. unplanned paths
- 155. 4. build the infrastructure
- 156. start small
- 157. build on what exists
- 158. borrow & reuse
- 159. you have to start somewhere
- 161. with metadata
Notes de l'éditeur
- enables findability
- Sometimes you want a broader contextSometimes you want a narrower context
- User facingNavigationTaxonomies & controlled vocabularies influence designLiquidDynamic
- Relational database format1:1, 1: Many relationshipsInfluences presentation If something is not stored properly it will not be displayed properly
- Semantic exchanges
- at least the ones that we are paid to design
- what was their last interaction like?
- what was their last interaction like?
- what was their last interaction like?
- watched star wars – mayber they’re interested in star trek