Skip to content

[ENHANCEMENT] Add metadata to assets to improve the search in M365LP: keywords #618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
harmsze opened this issue Jan 4, 2022 · 1 comment
Labels
type: enhancement New feature or request

Comments

@harmsze
Copy link

harmsze commented Jan 4, 2022

At this moment, users can only find information in Microsoft 365 Learning Pathways that is available inside our tenant, which means: custom pages you have added as assets, plus the metadata of playlists and assets. Not the full text of the assets that are stored in the Microsoft site (https://support.office.com) .

The problem: users cannot find the relevant playlists and assets in our M365LP portal, because we cannot squeeze all relevant search terms in the title and technology of assets and playlists or the description of playlists.

A solution: add a metadata field 'Keywords' to assets and playlists and search that in addition to the standard metadata (title etc)

1.Add a field in the form of Playlist > Edit Detail in CustomLearningAdmin.aspx. See attached screenshot.
We do not need to display the keywords to the end-users in the front-end of the playlist, only to the editors in the CustomLearningAdmin.

  • Type = Enterprise keywords (managed metadata, allow fill-in choices = yes) Or if that is too complex: Single line of text will already be helpful.
  • Mandatory? = No.
  • Placement = At the bottom of the set of fields
  • Other languages = Allow the editor to enter a translation (like in the Title and Description fields)
    GitHut-ProposalKeywordField20220104-Playlist

2.Add a field in in the form of Asset > Edit. See attached screenshot.
We do not need to display the keywords to the end-users in the front-end of the asset, only to the editors in the CustomLearningAdmin.

  • Same field as for Playlist
    GitHut-ProposalKeywordField20220104-Asset

3.Include the field Keywords in the search used by the M365LP web part (see screenshot), in addition to the title and the other standard metadata that are sort.
We do not need to display the keywords in the search results.
LPWebpart-Search-crop-EN-ann

It would be great if we can then also convince Microsoft to add these keywords to the content they provide for M365LP. But even if they don't add keywords to the standard playlists and assets, editors could at least make a copy and add the keywords to playlists and assets that are especially hard to find.

A better solution would be to allow the end-user to search the full text that is stored in the Microsoft site from our Microsoft 365 Learning Pathways portal, but that would probably be very difficult. Adding keywords is hopefully a relatively simple workaround.

And it would be a lot better if the search box that the users are most familiar with (namely: the site search at the top of the page) would also find playlists and assets, but I am aware of the difficulties. If we can at least find playlists and assets via the M365LP search by more than their title, technology and (for playlists) descrip[tion, that would already be very helpful.

@harmsze harmsze added the type: enhancement New feature or request label Jan 4, 2022
@dcashpeterson
Copy link
Contributor

@harmsze Thanks for the request. We have looked at full text search of the assets before and unfortunately because the content is iframed and we don't know where it might come from there isn't a way for us to do that. In addition, there is not a publicly available API for us to use for the Microsoft generated content on docs or support.

We can put custom keyword search on the backlog. If others are interesting in this feature it would be good to know the community desire for this so we are not just making decisions in a vacuum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants