How do you override #type of an item in an array in schema.org markup? - schema.org

in my #person section, I have the following
"alumniOf" : [
"Google",
"Autodesk",
"Wikimedia Foundation",
"Rhode Island School of Design"
],
Which resolves to
alumniOf
#type Organization
name Google
alumniOf
#type Organization
name Autodesk
alumniOf
#type Organization
name Wikimedia Foundation
alumniOf
#type Organization
name Rhode Island School of Design
the first 3 default #types are correct, but the last should be #type EducationalOrganization not Organization, how do I force the #type value?

Related

Is there a way to avoid generating "modules" root item from the treeview in doxygen?

I love the flexibility module-grouping gives you to customize the document structure. I am wondering if there is any way (configuration or custom code) to remove the automatically created "Modules" treeview layer?
<tab type="modules" visible="Yes" title=""/>
Note: I do not wish to change the title. I wish to remove the layer while keeping its children.
To the best of my knowledge there is no direct way to do this.
The following is a workaround but I don't know all the implications and side effects.
I did a small test with
/// \file
/// #defgroup grp1 First Group
/// the first group
/// #defgroup grp2 Second Group
/// the second group
In the file modules.js we see:
[ "First Group", "group__grp1.html", null ],
[ "Second Group", "group__grp2.html", null ]
In the file html/navtreedata.js we see:
[ "Modules", "modules.html", "modules" ],
When we replace this line with
[ "First Group", "group__grp1.html", null ],
[ "Second Group", "group__grp2.html", null ],
it looks like you get the requested result, but this workaround has to be done by hand and as written before the side effects are unknown.
As written by #JPGarza a side effect is:
if you click on some tree view items it won't remember the selection and the treeview will show a different current page.

How can I query delll boomi MDH field thats not in match rule?

I am new to MDH and I would like to know how to query MDH field directly thats not in match rules.
I have a model that has 5 fields (Src_id, name, email, updated_date, created_date) and we have a match rule on Src_id which is also ID in MDH.
But, I would like to search on name and get the Src_Id is it possible? if not, do I need to make any changes to my model
Any help is highly appreciated.
There are two avenues for "querying" your master data hub.
MDH Web UI
Boomi MDH API
You say you would like to search "Name" and get "Src_Id". If you using avenue
(1) - you simply go to UI and select "Add Filter"->"Field Data"->select "Name"->select operator "Equals"->{fill in name you'd like to search for} --> The entire Golden Record is returned and you can see it via the UI or by clicking the timestamp to pull up the record in depth
(2) refer to https://help.boomi.com/bundle/hub/page/r-mdm-REST_APIs.html
specifically "Query Golden Record". You would fill in all the necessary API information (URL)+Basic Auth based on Repository+universe id-based on model, etc.
Your request body would look like:
<RecordQueryRequest>
<view>
<fieldId>SRC_ID</fieldId>
</view>
<filter>
<fieldValue>
<fieldId>NAME</fieldId>
<operator>EQUALS</operator>
<value>{INSERT NAME TO SEARCH}</value>
</fieldValue>
</filter>
</RecordQueryRequest>
Response will be in XML corresponding to your model: eg)
<RecordQueryResponse resultCount="1" totalCount="1">
<Record recordId="GUID" createdDate="TIMESTAMP" updatedDate="TIMESTAMP" recordTitle="DERIVED BY MODEL">
<Fields>
<rootelementname>
<src_id>123</src_id>
</rootelementname>
</Fields>
</RecordQueryResponse>

How to correctly define schema for non-carousel category page and also satisfy consumer Google

Google mentions here that Carousel markups using ListItem with type, position and item is currently supported only for Recipe, Course and Article. So, doing this for other products is not much effective (looking at google search as the consumer).
Google in another page mentions this:
A category page listing several different products (or recipes, videos, or any other type). Each entity should be marked up using the relevant schema.org type, such as schema.org/Product for product category pages. However, if one item is marked, all items should be marked. Also, unless this is a carousel page, the marked items should not link out to separate details pages.
Note the statement about usage of proper Schema.org type, like Product and should not link to separate details pages.
So, for an online seller of shoes, then the category page will probably be like:
{
"#context": "http://schema.org",
"#type": "CollectionPage",
"#id": "https://www.example.com/cat1/cat2",
"url": "https://www.example.com/cat1/cat2",
"provider": {
"#type": "Organization",
"#id": "https://www.example.com#org"
},
"isPartOf": {
"#type": "WebSite",
"#id": "https://www.example.com#ws"
},
"name": "Running Shoes",
"hasPart": [
{
"#type": "Product",
"name": "shoe 1"
},{
"#type": "Product",
"name": "shoe 2"
},
...
]
}
I didn't use #id and url here, to conform with Google's statement about no link to separate details page. Don't feel comfortable about it.
Q1: Without these, how does this page semantically connect with the schemas of the respective products in other pages?
I didn't define the schema with ItemList as the items are not ordered and without position, SDTT raises error. (Infact, the above schema too raises error on SDTT with hasPart, stating: "Product is not a known valid target type for the hasPart property").
Q2: What is a better way to define this schema, to stay correct as per Schema.org and also not have Google raise errors?
Q3: If we use hasPart here for the products, can we on each of the product's ItemPage define isPartOf to include id-s to this CollectionPage (and other categories', if necessary) where the product is listed? Basically, that closes the loop, but as per schema, is that necessary or just one-way declaration (with 'hasPart' in category page) enough?

How can I add custom attributes to a "Product" type in with JSON-LD?

I have a real estate website which displays real estate properties for sale. For each page where a property is listed, I want to create JSON-LD code to display information about the property, using Schema.org.
I am not sure if there is a better type to use than Product for real estate listings here.
How can I add a custom attribute to describe the property?
Here is a JSON-LD structure for Product:
{
"#context": "https://schema.org/",
"#type": "Product",
"name": "address of the property ",
"image": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"description": "description about the houese"
}
}
I want to be able to add other info like
Primary Features
How many bedrooms it has
How many bathrooms it has
If it is a smart home or not
etc...
Interior Features
Fireplace
Fireplace location
etc...
Exterior Features
The Lots Size
Fets
etc...
How can I add these custom attribute that describes the property using Schema.org?
If you want to provide data about real estate, you need to use a type that represents real estate. Probably Accommodation (Apartment, House, …) for your case.
If you want to convey that this real estate is a product, you need to provide the Product type in addition to the Accommodation type.
Then you can use properties from Accommodation as well as Product.
{
"#context": "https://schema.org/",
"#type": ["House", "Product"],
"offers": {
"#type": "Offer"
},
"numberOfRooms": 4
}
Custom properties about the real estate can be added with the additionalProperty property, and, if applicable, with the amenityFeature property.

How to create tags? Docpad

How can I make the tags?
For example http://dogfeet.github.io
Are there other examples?
I'm add docpad-plugin-tagging but, Digital tags are not displayed alttest.herokuapp.com/tags/404.html :(
and how to create tags to one page alttest.herokuapp.com/posts/2013/2013-03-24_car_driving? Only Tags page, not all
my repo https://github.com/npofopr/_altyncev_test
You can add tags as an array or Comma Separated Value inside your meta data:
----
title: "My post title"
tags: "tag1 tag2 tag3"
----
Then access the tags for the current document via:
#document.tags