You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a measure to ensure our web entities are accurately consumed by bots we have a need for a scalable solution to implement correctly formatted templated schema markup via our enterprise CMS (QuickStart).
Is your feature request related to a problem? Please describe.
The Drupal schema.org Metatag is missing a component vital to our institution. We need to have the object type "CollegeOrUniversity" added, as this is the correct schema type to represent nearly all University of Arizona websites.
name
url
description
logo
image
sameAs
address
"@type": "PostalAddress",
streetAddress,
addressLocality
addressRegion
postalCode
addressCountry
telephone
email
parentOrganization
"@type": "EducationalOrganization",
"name": "University of Arizona",
"url": "https://www.arizona.edu/",
"address":
"@type": "PostalAddress",
"streetAddress": "1401 E University Blvd",
"addressLocality": "Tucson",
"addressRegion": "AZ",
"postalCode": "85721",
"addressCountry": "US"
Note: the ParentOrganization will always reference The University of Arizona, as such, the associated fields can contain default text.
For a better look at how the json should generate please see this google doc
Describe alternatives you've considered
Once this is completed there are more schema types to be added which round out nearly all use cases for the University of Arizona.
Roles and Permissions considerations
A clear and concise description of how each of the following roles would be impacted by this change:
Anonymous user
None
Authenticated user
None
Content editor
Would have the ability to create, modify, or delete content within the fields under the newly created "CollegeOrUniversity" type.
Content administrator
Would have the ability to create, modify, or delete content within the fields within the newly created "CollegeOrUniversity" type.
Administrator
Would have the ability to enable/disable the module and provide default nodes to each of the fields within the newly created "CollegeOrUniversity" type.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Motivation
As a measure to ensure our web entities are accurately consumed by bots we have a need for a scalable solution to implement correctly formatted templated schema markup via our enterprise CMS (QuickStart).
Is your feature request related to a problem? Please describe.
The Drupal schema.org Metatag is missing a component vital to our institution. We need to have the object type "CollegeOrUniversity" added, as this is the correct schema type to represent nearly all University of Arizona websites.
Proposed Resolution
Describe the solution you'd like
I would like for a new type of "CollegeOrUniversity" to be added to schema.org Metatag. Within this type the following fields should be available:
name
url
description
logo
image
sameAs
address
"@type": "PostalAddress",
streetAddress,
addressLocality
addressRegion
postalCode
addressCountry
telephone
email
parentOrganization
"@type": "EducationalOrganization",
"name": "University of Arizona",
"url": "https://www.arizona.edu/",
"address":
"@type": "PostalAddress",
"streetAddress": "1401 E University Blvd",
"addressLocality": "Tucson",
"addressRegion": "AZ",
"postalCode": "85721",
"addressCountry": "US"
Note: the ParentOrganization will always reference The University of Arizona, as such, the associated fields can contain default text.
For a better look at how the json should generate please see this google doc
Describe alternatives you've considered
Once this is completed there are more schema types to be added which round out nearly all use cases for the University of Arizona.
Roles and Permissions considerations
A clear and concise description of how each of the following roles would be impacted by this change:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: