Dynamic collection view or portal view for linked data entities

[Natkeeran]

Title (Goal)	Create a dynamic portal or landing page for linked data entities
Primary Actor	End user
Scope	Drupal View/Module
Level	Low
Story	As an end user, I would like to see all content related to a linked data entity in a portal or collection view. For example, if I go to a place entity, I would like to see all people from that place, all books that have this place as subject, all organizations located in this place etc.

[bryjbrown]

@Natkeeran Can you be a bit more specific on what you mean by "dynamic portal or landing page"?

I'm assuming two things here, the first is that you are using the term "entities" to refer to the types of objects defined in the 7.x Entities SP (which I usually call "authorities" to differentiate them from the "works" that we usually deal with). The second assumption is that you are asking for basically a standard display for these authorities, similar to how we would display a PDF or image object, with links to all the other resources connected to that authority.

Sorry if the language is kind of confusing here, but nailing down the vocab in these kinds of issues is important.

[Natkeeran]

@bryjbrown

I should have been more careful with the word entity. I meant all the "things" in an ontology that will have a uri (rdf resources, types!). For example, in the schema.org, they would include CreativeWork, Person, Organization, Place, Event etc.

What I am suggesting is creating a view that when the user goes to an instance of type, they get to browse all the other things (paged) it is linked to.

Examples:
https://tools.wmflabs.org/reasonator/?&q=172 (Place)
https://tools.wmflabs.org/reasonator/?q=Q76 (Person)

This type of portal/view will include authorities but not restricted to them. Anything with a uri can potentially have such a view.

Previously, if we need to collect heterogeneous data about something in 7.x, we would have to create a collection. I think with the linked data approach, it can be dynamically generated.

[seth-shaw-unlv]

My migrate proof-of-concept implements an example of this. After import each image has an entity link to applicable subjects (each subject term is a node) and the subject nodes have a view-block listing all the images that link to that subject node.

It is pretty simple to build using the view interface.

[Natkeeran]

@seth-shaw-unlv

I was able to import the nodes. But, I cannot quite test this out because of the node has term issue related to placing the block. As you noted, a lot of the functionality can be build using views.

[seth-shaw-unlv]

Okay. I hadn't looked at it since the giant content model overhaul was finally committed, so there may have been a change along the way that broke it. I will have to play with it later.

[seth-shaw-unlv]

Oh, @Natkeeran, if you wouldn't mind posting what you saw to the proof-of-concept issues, I would appreciate it.

[Natkeeran]

@seth-shaw-unlv

I don't think the issue is related to the proof-of-concept module. It is the original issue you found related to that big PR where you cannot place any block without specifying a term. We decided to address the issue after PR gets in, but not sure if there is a ticket to followup on that issue.