{"id":516629,"date":"2021-06-04T11:30:54","date_gmt":"2021-06-04T09:30:54","guid":{"rendered":"https:\/\/www.devoteam.com\/expert-view\/wardrobe-wisdom-the-magic-of-metadata\/"},"modified":"2021-06-04T11:30:54","modified_gmt":"2021-06-04T09:30:54","slug":"wardrobe-wisdom-the-magic-of-metadata","status":"publish","type":"expert-view","link":"https:\/\/devoteam.info\/lu\/expert-view\/wardrobe-wisdom-the-magic-of-metadata\/","title":{"rendered":"Wardrobe Wisdom : The Magic Of Metadata"},"content":{"rendered":"

Content can be stored in different categories or in different ways on intranets, but the result is often the same : it takes time to find it, it\u2019s not efficient, and the whole experience is a nightmare for both the end-user and the manager of the platform. So, what solutions do we have? In this article, we will see how using metadata to store content can improve the experience.<\/p>\n

<\/p>\n

\"messy-desk-computer\"<\/p>\n

\"circle-cropped Written by Soline De Dorlodot, Change and Intranet Manager at Devoteam G Cloud<\/span><\/em><\/p>\n

A traditional intranet is like a closet : you have to store each type of content in a specific location. In general, whether you are trying to find a jumper in a closet or a procedure on the intranet, you do not remember exactly where it is. Instead, you rely on the storage logic of the dressing room or the intranet.<\/p>\n

For example, you may find your jumper quickly, because you know that all the jumpers are on the left-hand shelf. Similarly, you can find FAQs without trouble because you know that they are filed under the “Support” label of the intranet. In both cases, it will not take much effort for the user to find what he\/she is looking for.<\/p>\n

One file, several locations<\/h2>\n

Things get tricky when content can be stored in more than one place : is my red jumpsuit with my trousers or with my dresses? Is the procedure for requesting leave under “HR” or under “Procedure”? <\/p>\n

\"confused-woman-intranet-computer\"<\/p>\n

Now, let’s assume that the person who manages our intranet\/closet is a bit messy (like me). Soon, the contents pile up on top of each other in an inextricable mess. The content our users are looking for becomes very hard to find.<\/p>\n

The user of the dressing room might end up wearing another outfit, feeling less comfortable, and not approaching his crush as a result. That’s the potential love of his life gone! As for the intranet user, she may give up requesting leave in a formal way. She’ll go to Barbados with her family and discover on her return that she’s been fired for serious misconduct.<\/p>\n

Obviously, both these scenarios are unlikely to happen. What is certain, however, is that our two users would have lost a lot of time.<\/p>\n

How to solve this conundrum?<\/h2>\n

Fed up, the fashion enthusiast decides to digitise the contents of his closet so that it can be managed through an application. He will take photos of his clothes and list them with the help of virtual tags, commonly called metadata<\/span>. To compose an outfit, he’ll just have to search the characteristics of the clothes he is looking for. What a time saver!<\/p>\n

\"pair-of-jeans\"<\/p>\n

Type: Pants<\/em><\/span>
Colour: Blue<\/em><\/span>
Season: Winter<\/em><\/span>
Size: M<\/em><\/span>
Brand: XYZ<\/em><\/span><\/p>\n

<\/p>\n

As for the intranet user, she reports her struggles to the manager of the platform. The decision is made to move to another intranet, one that doesn’t work like traditional ones with a content tree. This time, the intranet must organise content using metadata. Their choice leads them to LumApps<\/strong><\/a>.<\/p>\n

<\/p>\n

\"intranet-screenshot-example\"Type: Procedure<\/em>
Department: HR<\/em>
Subsidiaries: Antwerp and Ghent<\/em><\/p>\n

She will also be able to choose who the information is intended for – in this case, all the employees in the company.<\/em><\/p>\n

The use of metadata will allow the intranet manager to :<\/p>\n