Skip to content

[METADATA UPDATE][Merge by 2024-03-29] Global reporting metadata update#43

Merged
huypub merged 1 commit intomainfrom
58cca3f0-4e59-4c4f-b2f2-97c2ba690e3d_18
Mar 26, 2024
Merged

[METADATA UPDATE][Merge by 2024-03-29] Global reporting metadata update#43
huypub merged 1 commit intomainfrom
58cca3f0-4e59-4c4f-b2f2-97c2ba690e3d_18

Conversation

@learn-build-service-prod
Copy link

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 docs-allowlist-mgmt@microsoft.com. If you are not the correct contact for this content and repository, please notify Metadata-Management@microsoft.com.

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 Metadata-Management@microsoft.com if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.

Fixing#929448 Remove ms.service = active-directory paired with ms.subservice = develop. Replaced by ms.service = identity-platform

Why is reporting metadata being updated?
The C+E Skilling Content Architecture team manages the Learn platform's reporting taxonomies that enable content analytics for OKR reporting and content portfolio management. Reporting taxonomy values populate metadata attributes.

We regularly review reporting taxonomies to ensure they are accurate, useful, and align to current business needs. Updates to reporting taxonomies and associated metadata make reports cleaner, easier to use, and more consistent.

Why are ms.prod and ms.technology metadata being moved to ms.service and ms.subservice?
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.

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 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.

…lop. Replaced by ms.service = identity-platform
@kasangi
Copy link

kasangi commented Mar 26, 2024

@shlipsey3 @thomps23 please review and signoff, thanks!

@v-emilypr
Copy link

#please-close

@learn-build-service-prod
Copy link
Author

Learn Build status updates of commit 952a4bc:

⚠️ Validation status: warnings

File Status Preview URL Details
msal/docfx.json ⚠️Warning Details
msal/overview/msal-overview.md ✅Succeeded View (msal-js-latest)

msal/docfx.json

  • Line 77, Column 32: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.subservice': 'msal-js' is not valid with 'ms.service' value 'identity-platform'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@huypub huypub merged commit 7acc63a into main Mar 26, 2024
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.

4 participants