search

CDRH / earlywashingtondc

OSCYS Rails site
http://earlywashingtondc.org
2 stars 0 forks source link

RDF Datastore Configuration #99

Open jduss4 opened 9 years ago

jduss4 commented 9 years ago

Now that I have found out that Fuseki isn't using my config file and HOW to get it to use the config file https://github.com/ewg118/xEAC/wiki/Deploying-Fuseki

should we make it so that OSCYS has an actual endpoint that we could point people towards? I was able to remove the update / upload ability for it so it would be safe. It would be harder for Laura to update, however, as it would involve putting a file in a weird location on the server and restarting fuseki.

Regardless I should probably update cdrhsites so that nobody can post random stuff in the default datastore on there. :)

jduss4 commented 9 years ago

Findings: I have figured out how to make a default read-only service that uses a file from the filesystem. I doubt that it will be faster than our current setup but it would mean Laura wouldn't need to worry about fuseki at all, unless if it is holding the file in memory and would need to be restarted (TODO look into that) but otherwise I think we could then expose the endpoint as a way to peruse our RDF. Might add an OWL endpoint as well.

Also: I've been using "rdf" as the prefix for the rdf schema but it looks like the standard is to use prefix "rdfs"

jduss4 commented 9 years ago

Crud, so actually this won't work at all because the fuseki endpoint is on cdrhsearch and I need the rdf files on cdrhsites. :( We could still manually load it onto cdrhsearch if we want another step in the process, though

karindalziel commented 9 years ago

Moved to v3 - do this when data has stopped changing

jduss4 commented 5 years ago

Several years later update: the data has not stopped changing :P