Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into ultraPortal

roygara · roygara · commit e04892243ee7 · 2019-11-15T09:27:28.000-08:00
diff --git a/articles/cognitive-services/Academic-Knowledge/PaperEntityAttributes.md b/articles/cognitive-services/Academic-Knowledge/PaperEntityAttributes.md
@@ -9,16 +9,15 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: academic-knowledge
 ms.topic: conceptual
-ms.date: 10/22/2019
+ms.date: 11/14/2019
 ms.author: darrine
 ROBOTS: NOINDEX
 ---
 
 # Paper Entity
 
-<sub>
-*Below attributes are specific to paper entity. (Ty = '0')
-</sub>
+> [!NOTE]
+> Below attributes are specific to paper entity. (Ty = '0')
 
 Name | Description | Type | Operations
 --- | --- | --- | ---
@@ -29,43 +28,78 @@ AA.AuN | Normalized author name | String | Equals, StartsWith
 AA.DAuN | Original author name | String | None
 AA.DAfN | Original affiliation name | String | None
 AA.S | Numeric position in author list | Int32 | Equals
-CC | Citation count | Int32 | None  
+BT | BibTex document type ('a':Journal article, 'b':Book, 'c':Book chapter, 'p':Conference paper) | String | None
+BV | BibTex venue name | String | None
 C.CId | Conference series ID | Int64 | Equals
 C.CN | Conference series name | String | Equals, StartsWith
+CC | Citation count | Int32 | None  
+CitCon | Citation contexts</br></br>List of referenced paper ID’s and the corresponding context in the paper (e.g. [{123:["brown foxes are known for jumping as referenced in paper 123", "the lazy dogs are a historical misnomer as shown in paper 123"]}) | Custom | None
 D | Date published in YYYY-MM-DD format | Date | Equals, IsBetween
-E | Extended metadata (see table below) | String | N/A  
+DN | Original paper title | String | None
+DOI | Digital Object Identifier | String | Equals, StartsWith
+E | Extended metadata</br></br>**IMPORTANT**: This attribute has been deprecated and is only supported for legacy applications. Requesting this attribute individually (i.e. attributes=Id,Ti,E) will result in all extended metadata attributes being returned in a *serialized JSON string*</br></br>All attributes contained in the extended metadata are now available as a top-level attribute and can be requested as such (i.e. attributes=Id,Ti,DOI,IA) | [Extended](#extended) | None
 ECC | Estimated citation count | Int32 | None
 F.DFN | Original field of study name | String | None
 F.FId | Field of study ID | Int64 | Equals
 F.FN | Normalized field of study name | String | Equals, StartsWith
+FP | First page of paper in publication | String | Equals
+I | Publication issue | String | Equals
+IA | Inverted abstract | [InvertedAbstract](#invertedabstract) | None
 Id | Paper ID | Int64 | Equals
 J.JId | Journal ID | Int64 | Equals
 J.JN | Journal name | String | Equals, StartsWith
+LP | Last page of paper in publication | String | Equals
+PB | Publisher | String | None
 Pt | Publication type (0:Unknown, 1:Journal article, 2:Patent, 3:Conference paper, 4:Book chapter, 5:Book, 6:Book reference entry, 7:Dataset, 8:Repository | String | Equals
 RId | List of referenced paper IDs | Int64[] | Equals
+S | List of source URLs of the paper, sorted by relevance | [Source](#source)[] | None
 Ti | Normalized title | String | Equals, StartsWith
+V | Publication volume | String | Equals
+VFN | Full name of the Journal or Conference venue | String | None
+VSN | Short name of the Journal or Conference venue | String | None
 W | Unique words in title | String[] | Equals
 Y | Year published | Int32 | Equals, IsBetween
 
-## Extended Metadata Attributes ##
+## Extended
+> [!IMPORTANT]
+> This attribute has been deprecated and is only supported for legacy applications. Requesting this attribute individually (i.e. attributes=Id,Ti,E) will result in all extended metadata attributes being returned in a *serialized JSON string*</br></br>All attributes contained in the extended metadata are now available as a top-level attribute and can be requested as such (i.e. attributes=Id,Ti,DOI,IA)
+
+> [!IMPORTANT]
+> Support for requesting individual extended attributes by using the "E." scope, i.e. "E.DN" is being deprecated. While this is still technically supported, requesting individual extended attributes using the "E." scope will result in the attribute value being returned in two places in the JSON response, as part of the "E" object and as a top level attribute.
+
+Name | Description | Type | Operations
+--- | --- | --- | ---
+BT | BibTex document type ('a':Journal article, 'b':Book, 'c':Book chapter, 'p':Conference paper) | String | None
+BV | BibTex venue name | String | None
+CC | Citation contexts</br></br>List of referenced paper ID’s and the corresponding context in the paper (e.g. [{123:["brown foxes are known for jumping as referenced in paper 123", "the lazy dogs are a historical misnomer as shown in paper 123"]}) | Custom | None
+DN | Original paper title | String | None
+DOI | Digital Object Identifier | String | None
+FP | First page of paper in publication | String | None
+I | Publication issue | String | None
+IA | Inverted Abstract | [InvertedAbstract](#invertedabstract) | None
+LP | Last page of paper in publication | String | None
+PB | Publisher | String | None
+S | List of source URLs of the paper, sorted by relevance | [Source](#source)[] | None
+V | Publication volume | String | None
+VFN | Full name of the Journal or Conference venue | String | None
+VSN | Short name of the Journal or Conference venue | String | None
+
+## InvertedAbstract
+
+> [!IMPORTANT]
+> InvertedAbstract attributes cannot be directly requested as a return attribute. If you need an individual attribute you must request the top level "IA" attribute, i.e. to get IA.IndexLength request attributes=IA
 
-Name | Description               
---- | ---
-BT | BibTex document type ('a':Journal article, 'b':Book, 'c':Book chapter, 'p':Conference paper)
-BV | BibTex venue name
-CC | Citation Contexts – List of referenced paper ID’s and the corresponding context in the paper (e.g. [{123:["brown foxes are known for jumping as referenced in paper 123", "the lazy dogs are a historical misnomer as shown in paper 123"]})
-DN | Original paper title
-DOI | Digital Object Identifier
-FP | First page of paper in publication
-I | Publication issue
-IA | Inverted Abstract
-IA.IndexLength | Number of items in the index (abstract's word count)
-IA.InvertedIndex | List of abstract words and their corresponding position in the original abstract (e.g. [{"the":[0, 15, 30]}, {"brown":[1]}, {"fox":[2]}])
-LP | Last page of paper in publication
-PB | Publisher
-S | Sources - list of web sources of the paper, sorted by static rank
-S.Ty | Source Type (1:HTML, 2:Text, 3:PDF, 4:DOC, 5:PPT, 6:XLS, 7:PS)
-S.U | Source URL
-V | Publication volume
-VFN | Full name of the Journal or Conference venue
-VSN | Short name of the Journal or Conference venue
+Name | Description | Type | Operations
+--- | --- | --- | ---
+IndexLength | Number of items in the index (abstract's word count) | Int32 | None
+InvertedIndex | List of abstract words and their corresponding position in the original abstract (e.g. [{"the":[0, 15, 30]}, {"brown":[1]}, {"fox":[2]}]) | Custom | None
+
+## Source
+
+> [!IMPORTANT]
+> Source attributes cannot be directly requested as a return attribute. If you need an individual attribute you must request the top level "S" attribute, i.e. to get S.U request attributes=S
+
+Name | Description | Type | Operations
+--- | --- | --- | ---
+Ty | Source URL type (1:HTML, 2:Text, 3:PDF, 4:DOC, 5:PPT, 6:XLS, 7:PS) | String | None
+U | Source URL | String | None
diff --git a/articles/lighthouse/concepts/cloud-solution-provider.md b/articles/lighthouse/concepts/cloud-solution-provider.md
@@ -13,7 +13,7 @@ manager: carmonm
 
 If you're a [CSP (Cloud Solution Provider)](https://docs.microsoft.com/partner-center/csp-overview) partner, you can already access the Azure subscriptions created for your customers through the CSP program by using the [Administer On Behalf Of (AOBO)](https://channel9.msdn.com/Series/cspdev/Module-11-Admin-On-Behalf-Of-AOBO) functionality. This access allows you to directly support, configure, and manage your customers' subscriptions.
 
-With Azure Lighthouse, you can use Azure delegated resource management along with AOBO. This helps improve security and reduces unnecessary access by enabling more granular permissions for your users. It also allows for greater efficiency and scalability, as your users can work across multiple customer subscriptions using a single login in your tenant.
+With [Azure Lighthouse](../overview.md), you can use Azure delegated resource management along with AOBO. This helps improve security and reduces unnecessary access by enabling more granular permissions for your users. It also allows for greater efficiency and scalability, as your users can work across multiple customer subscriptions using a single login in your tenant.
 
 > [!TIP]
 > To help safeguard customer resources, be sure to review and follow our [recommended security practices](recommended-security-practices.md) along with the [partner security requirements](https://docs.microsoft.com/partner-center/partner-security-requirements).
diff --git a/articles/lighthouse/concepts/enterprise.md b/articles/lighthouse/concepts/enterprise.md
@@ -11,7 +11,7 @@ manager: carmonm
 
 # Azure Lighthouse in enterprise scenarios
 
-The most common scenario for Azure Lighthouse is a service provider managing resources in its customers’ Azure  Active Directory (Azure AD) tenants. However, the capabilities of Azure Lighthouse can also be used to simplify cross-tenant management within an enterprise which uses multiple Azure AD tenants.
+The most common scenario for [Azure Lighthouse](../overview.md) is a service provider managing resources in its customers’ Azure  Active Directory (Azure AD) tenants. However, the capabilities of Azure Lighthouse can also be used to simplify cross-tenant management within an enterprise which uses multiple Azure AD tenants.
 
 ## Single vs. multiple tenants
 
diff --git a/articles/lighthouse/how-to/deploy-policy-remediation.md b/articles/lighthouse/how-to/deploy-policy-remediation.md
@@ -11,7 +11,7 @@ manager: carmonm
 
 # Deploy a policy that can be remediated within a delegated subscription
 
-Azure Lighthouse allows service providers to create and edit policy definitions within a delegated subscription. However, to deploy policies that use a [remediation task](https://docs.microsoft.com/azure/governance/policy/how-to/remediate-resources) (that is, policies with the [deployIfNotExists](https://docs.microsoft.com/azure/governance/policy/concepts/effects#deployifnotexists) or [modify](https://docs.microsoft.com/azure/governance/policy/concepts/effects#modify) effect), you’ll need to create a [managed identity](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview) in the customer tenant. This managed identity can be used by Azure Policy to deploy the template within the policy. There are steps required to enable this scenario, both when you onboard the customer for Azure delegated resource management, and when you deploy the policy itself.
+[Azure Lighthouse](../overview.md) allows service providers to create and edit policy definitions within a delegated subscription. However, to deploy policies that use a [remediation task](https://docs.microsoft.com/azure/governance/policy/how-to/remediate-resources) (that is, policies with the [deployIfNotExists](https://docs.microsoft.com/azure/governance/policy/concepts/effects#deployifnotexists) or [modify](https://docs.microsoft.com/azure/governance/policy/concepts/effects#modify) effect), you’ll need to create a [managed identity](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview) in the customer tenant. This managed identity can be used by Azure Policy to deploy the template within the policy. There are steps required to enable this scenario, both when you onboard the customer for Azure delegated resource management, and when you deploy the policy itself.
 
 ## Create a user who can assign roles to a managed identity in the customer tenant
 
diff --git a/articles/lighthouse/how-to/policy-at-scale.md b/articles/lighthouse/how-to/policy-at-scale.md
@@ -11,7 +11,7 @@ manager: carmonm
 
 # Deploy Azure Policy to delegated subscriptions at scale
 
-As a service provider, you may have onboarded multiple customer tenants for Azure delegated resource management. Azure Lighthouse allows service providers to perform operations at scale across several tenants at once, making management tasks more efficient.
+As a service provider, you may have onboarded multiple customer tenants for Azure delegated resource management. [Azure Lighthouse](../overview.md) allows service providers to perform operations at scale across several tenants at once, making management tasks more efficient.
 
 This topic shows you how to use [Azure Policy](https://docs.microsoft.com/azure/governance/policy/) to deploy a policy definition and policy assignment across multiple tenants using PowerShell commands. In this example, the policy definition ensures that storage accounts are secured by allowing only HTTPS traffic.
 
