search

srophe / srophe-eXist-app

DEPRECATED eXist code for Syriaca.org: The Syriac Reference Portal
GNU General Public License v3.0
10 stars 11 forks source link

Legacy data (?) in SPEAR #1113

Closed dlschwartz closed 6 years ago

dlschwartz commented 6 years ago

@wsalesky The first thing I noticed is that the sex element data is still appearing and the trait type="gender" data is not appearing. This is the case even though there are no longer any sex elements in the tei. This appears to be the case only on the browse pages, which suggests a SPARQL problem. If you do a keyword search for female you get many hits.

Then I noticed the following oddity: I just wanted to look at the Chronicle events to check the pulling in of the Syriac from the Corpus. browsechron

When I selected "See more", it took me here: browsechronselect

However, when I searched for "the Daisan river flooded Edessa", it took me here: searchchronevent

Note the different URI numbers. That change was made about three weeks ago: https://github.com/srophe/srophe-app-data/commit/fe8c0b2de1b79127c51740fc6b45e7da77503cfe#diff-6a6705da5bed7bae3566a94792915338. It looks like the new data shows up when accessed through search but that old data is still visible in browse.

wsalesky commented 6 years ago

Hum, that seems to indicate a problem with the RDF generation. I think I will need to investigate this tonight.

dlschwartz commented 6 years ago

@wsalesky Thanks Winona. I hope this doesn't take too much time. I wish I had caught this earlier but I had tunnel vision regarding the data cleaning. I have a few small changes to the tei to make. I'll do that before lunch so that you can re-run the rdf. I'll try not to make any changes after that. Thank you.

dlschwartz commented 6 years ago

Oh, and I might not be updating the RDF correctly. I select "run" here (http://wwwb.library.vanderbilt.edu/exist/apps/srophe/sparql/update-rdf.html) and it doesn't give me much indication of anything happening. I've selected "run" a handful of times in the last three weeks. Perhaps I've never actually run anything.

wsalesky commented 6 years ago

I'm going to work on it tonight, after 8 EST. As for the update rdf, it takes a long time, and on the dev server gets a server timeout message, however, it does continue to run in the background after returning the error. So while not very informative on the dev server it is running. I suspect a combination of RDF generation problems and SPARQL issues. Hopefully I can get it all fixed tonight for you.

dlschwartz commented 6 years ago

Okay, thanks Winona!

wsalesky commented 6 years ago

@dlschwartz I think this one is fixed as well.