search

ualbertalib / can-link

Front end react app for CanLink project
1 stars 0 forks source link

Create page for individual subjects #56

Closed sfarnel closed 3 years ago

sfarnel commented 3 years ago

Create a separate page for individual subjects?(e.g. http://206.167.181.124:8000/getitem/http://canlink.library.ualberta.ca/subject/e52aafb06de949864871fd8885da9b04)

jchartrand commented 3 years ago

@sfarnel

Does this mean create a new HTML page in can-link that maybe more nicely formats and displays the subject info that comes out of the triple store?

Or would we put the some specific set of subject related data into SOLR and I'd create a page to show that data?

sfarnel commented 3 years ago

Thanks @jchartrand I think what we have in mind here (@danydvd chime in also!) is the first option, i.e., a page that shows the info for the subject as well as items that have that subject.

danydvd commented 3 years ago

Thanks @jchartrand. I agree @sfarnel that first option is what I was thinking too. For this we can use the subject_url (in SOLR) and query the triple to get all fields in the subject.

jchartrand commented 3 years ago

@danydvd I guess this is actually pretty similar to #57 at least in so far as we'd probably use the same SPARQL query?

So, like with #57, how would I run a SPARQL query from the web browser - is there a RESTful endpoint?

jchartrand commented 3 years ago

@danydvd As with #57 - can you enable CORS on the sparql endpoint? I need to pull the RDF in using XHR (therefore need the CORS) and then render the RDF nicely.

jchartrand commented 3 years ago

@sfarnel @danydvd

The new subject page will be linked from the subjects listed on the thesis record page?

i.e., from:

image
sfarnel commented 3 years ago

Thanks @jchartrand yes, I think this makes the most sense. What do you think @danydvd

danydvd commented 3 years ago

@jchartrand I agree. Each subject in the subjects list would be link to its own page.

jchartrand commented 3 years ago

@sfarnel @danydvd

I've created the Subject page, but I've discovered that there isn't really anything to show from the returned RDF, other than the label. The other triples wouldn't (I don't think) mean much to people, but maybe I'm wrong.

So, I just show whatever RDF is available, with a 'select' dropdown with which to choose the serialization.

I'm not sure what I could show other than the RDF. I guess I could possibly render the triples in something like a three column grid (subject, predicate, object), but that probably wouldn't look much different than turtle/n3.

sfarnel commented 3 years ago

Thanks @jchartrand A couple thoughts; @danydvd chime in as well:

I think we were also wondering about showing the identifiers for all items that have that subject It might be nice to have a more user friendly format for display; maybe we can add this after the fact

sfarnel commented 3 years ago

Complete. Closing issue