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-04-12] Retiring the ms.prod and ms.technology metadata attributes from the Learn platform (values moving to ms.service) #1830

Merged
merged 1 commit into from
Mar 29, 2024

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#944254 Allowlist Request 944254 Remove ms.prod value excel

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

  • C+E Skilling Site Experience 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.
  • In Germanium, we are retiring the ms.prod/ms.technology attributes and migrating metadata to the ms.service/ms.subservice attributes. 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.

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.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
ms.prod = excel

Replace with

ms.service = excel
Copy link
Contributor Author

Learn Build status updates of commit 128e4d7:

✅ Validation status: passed

File Status Preview URL Details
api/Excel.AboveAverage.SetFirstPriority.md ✅Succeeded View
api/Excel.Action.md ✅Succeeded View
api/Excel.Action.Type.md ✅Succeeded View
api/Excel.Actions.Application.md ✅Succeeded View
api/Excel.Actions.Count.md ✅Succeeded View
api/Excel.Actions.Item.md ✅Succeeded View
api/Excel.Actions.md ✅Succeeded View
api/Excel.AddIn.Parent.md ✅Succeeded View
api/Excel.AddIns.Count.md ✅Succeeded View
api/Excel.AddIns.Item.md ✅Succeeded View
api/Excel.AddIns2.Count.md ✅Succeeded View
api/Excel.AddIns2.Item.md ✅Succeeded View
api/Excel.Adjustments.Item.md ✅Succeeded View
api/Excel.AllowEditRanges.Count.md ✅Succeeded View
api/Excel.Application.ActiveCell.md ✅Succeeded View
api/Excel.Application.ActiveChart.md ✅Succeeded View
api/Excel.Application.ActivePrinter.md ✅Succeeded View
api/Excel.Application.ActiveProtectedViewWindow.md ✅Succeeded View
api/Excel.Application.AutomationSecurity.md ✅Succeeded View
api/Excel.Application.Caller.md ✅Succeeded View
api/Excel.Application.ClusterConnector.md ✅Succeeded View
api/Excel.Application.COMAddIns.md ✅Succeeded View
api/Excel.Application.CopyObjectsWithCells.md ✅Succeeded View
api/Excel.Application.DDEAppReturnCode.md ✅Succeeded View
api/Excel.Application.DDEPoke.md ✅Succeeded View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.

For any questions, please:

@lindalu-MSFT lindalu-MSFT merged commit cb72291 into main Mar 29, 2024
2 checks passed
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.

None yet

1 participant