Skip to content
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

[METADATA UPDATE][Merge by 2024-02-07] Retiring the ms.prod and ms.technology metadata attributes from the Learn platform (values moving to ms.service) #1032

Conversation

learn-build-service-prod[bot]
Copy link
Contributor

A Pull Request has been made from the Learn Platform's Metadata Management System. Please review and merge this Pull Request within 5 days. If you have any questions or concerns about the purpose of these metadata updates, please contact [email protected]. If you are not the correct contact for this content and repository, please notify [email protected].

If this Pull Request is not merged within 14 days, it will be automatically merged by our system to ensure the timeliness of the metadata update. This includes bypassing the Repository's Branch Policy, including if Review Required is enabled. Please notify [email protected] if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.

Fixing#930735 Remove ms.technology = iis-troubleshoot paired with ms.prod = iis. Replaced by ms.subservice = troubleshoot paired with ms.service = iis
Fixing#930730 Remove ms.technology = iis-hosting paired with ms.prod = iis. Replaced by ms.subservice = web-hosting paired with ms.service = iis
Fixing#930745 Remove ms.technology = iis-extensions paired with ms.prod = iis. Replaced by ms.subservice = extensions paired with ms.service = iis
Fixing#930733 Remove ms.technology = iis-appfx paired with ms.prod = iis. Replaced by ms.subservice = appfx paired with ms.service = iis
Fixing#930742 Remove ms.technology = iis-publish paired with ms.prod = iis. Replaced by ms.subservice = publish paired with ms.service = iis
Fixing#930732 Remove ms.technology = iis-config paired with ms.prod = iis. Replaced by ms.subservice = config-reference paired with ms.service = iis
Fixing#930752 Remove ms.technology = iis-manage paired with ms.prod = iis. Replaced by ms.subservice = mgmt paired with ms.service = iis
Fixing#930741 Remove ms.technology = iis-develop paired with ms.prod = iis. Replaced by ms.subservice = develop paired with ms.service = iis

Summary
In Germanium, the ms.prod and ms.technology metadata attributes will be retired from the Learn platform and values will be consolidated into ms.service and ms.subservice for reporting on content by product.

  • C+E Skilling Content Architecture manages internal, business-facing taxonomies that enable reporting on key metrics for content published on Microsoft Learn. Authors manually apply values from these taxonomies to populate metadata attributes.
  • Two of these taxonomies are ms.prod/ms.technology and ms.service/ms.subservice. "ms.prod" and "ms.service" were distinctions carried over from legacy systems that predated the Learn platform, intended to differentiate on-prem products from cloud services.
  • We plan to rename the attributes from ms.service and ms.subservice in a future semester.

Why are we making this change?

  • For the business: Accuracy of reporting metadata directly impacts the accuracy of content analytics, so it's important that related taxonomies reflect the current state of the business. Most product taxonomies within Microsoft no longer distinguish between "on-prem" and "cloud service."
  • For content authors: We eliminate the need to choose between two similar attributes when applying reporting metadata to content or filtering reports.
  • For engineers, data scientists, and taxonomists: Simplifying and reducing underlying metadata attributes reduces the cost and complexity required to extend metadata capabilities on the platform.

How does this affect me?

  • Once changes to reporting metadata are merged, dashboards and reports maintained by Skilling Insights & Intelligence will reflect new values. If you've been using ms.prod/ms.technology filters, you'll switch to ms.service/ms.subservice filters in those dashboards and reports.
  • If you have custom dashboards or Kusto queries, you might need to update those as well.

Frequently Asked Questions
Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.

  • For Git Repos with a permissioned Service Account, we open the PR from our Document Build Service Account.
  • For Git Repos that we either do not have Service Account permission for or the repo is in Azure Repos (ADO) we open the Pull Requests in an automated way with the PR creator as the Repo owner.

How can I revert a Pull Request that has been merged and created an unexpected issue? Whether a PR has been merged manually or automatically, you can revert it if an issue arises. See Reverting a pull request - GitHub Docs.

@learn-build-service-prod learn-build-service-prod bot requested a review from a team as a code owner January 24, 2024 17:07
@learn-build-service-prod learn-build-service-prod bot merged commit 56f276b into Metadata_Refactor_71f0bf01-6309-435b-97ff-a70cc74fbfcd Jan 30, 2024
2 checks passed
@learn-build-service-prod learn-build-service-prod bot deleted the 71f0bf01-6309-435b-97ff-a70cc74fbfcd_82 branch January 30, 2024 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants