Page History

• Models

• and vocabularies are complete and

• pass ad-hoc testing in rails console

• Models use the ActiveTriples gem

• owner, contributors - Need to look into PROV ontology (per suggestion from Paolo)
• lists - There are still discussions about whether to represent lists as ORE or Collections.  I plan to wait until I am further along and know more about the implications for implementation for each model.

• The test for the first model is close to being complete, but not sure what issues will arise

• in the final tests
• The others should be quick to write since they are going to be very similar to the tests for the first model

• This is likely really close to complete.  The setup is similar to that used by the demo presented at the June 2014 Stanford meeting. It's status as marked low because I haven't tested it yet.

• The persistence to the triplestore is handled by the ActiveTriples::Resource class. In the process of testing the persistence mechanism through the rspec tests for models.

• I have located some code in ActiveTriple gem's rspec tests that manipulates SOLR.  I need to explore this further.

• The queries are currently defined as SPARQL queries, so they need to be rewritten as SOLR queries.

• I have information from Jim Blake about how to get the information from VIVO

• . It involves getting the information through a curl command and then parsing the returned result.
• Need to write code to do the conversion.  (Was hoping for a webservice written by VIVO that did this.)

The clone runs locally on my machine and in my dev environment.

Questions:

• Should the code go into LD4L GitHub or Cornell GitHub.  It is a direct clone of the CULIT Discovery and Access system.

• I've explored the code to see where some of the changes need to be made, but I haven't made any changes yet.  I want to get the cloned code in a source code repository before beginning to make modifications.

I have been corresponding with Tom Johnson (the developer of ActiveTriples).