You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@davidamichelson@dlschwartz How would you like me to handle this issue? We are not quite ready to start querying the triplestore, but I don't want to leave these broken. I can generate the linked data as static html with the pages, and then we can either run an update, or make just that part of the page dynamic one the triplestore is back up. Or I can just hide it for now.
Let me know your preferences, I can working on getting all of the apps into the new workflow, which is require some updates to all the application functions, and running static HTML pages, in addition to adding the workflow branch.
The text was updated successfully, but these errors were encountered:
I'm not sure about what's best in the short term. I might need to discuss this to better understand the issues.
For the mid term, I've been pushing really hard to clean SBD so we can serialize it. This has highlighted some issues in places that need an update as well. This work is coming along. I hope to begin a discussion on Wednesday about what data from persons and places we want to serialize. I don't expect that every bit will get in. I hope to have clean (enough?) data, all of the things we want to serialize, and all of the xml paths laid out (as we did with SPEAR) by the end of the summer.
Since persons, places, and SPEAR are integrated with the Taxonomy, an update on this data and its serialization are also an important components of implementing RDF. I'm working on needed concepts but also on issues of data model and workflow.
@dlschwartz I would like to get gedsh set up on the new workflow by the end of the week, I am planning on serializing all the articles as HTML, and would like to have some sort of fix before I run the HTML. It is very easy to rerun this and update it once the SBD data is up to date, but we need some sort of short term solution so I am not publishing obviously broken data. My preference would be to hard code the linked data into the HTML output for the first run, and then either update it, or make that part of the page dynamic once we have the RDF ready to go. What do you think?
@davidamichelson @dlschwartz How would you like me to handle this issue? We are not quite ready to start querying the triplestore, but I don't want to leave these broken. I can generate the linked data as static html with the pages, and then we can either run an update, or make just that part of the page dynamic one the triplestore is back up. Or I can just hide it for now.
Let me know your preferences, I can working on getting all of the apps into the new workflow, which is require some updates to all the application functions, and running static HTML pages, in addition to adding the workflow branch.
The text was updated successfully, but these errors were encountered: