Applied Linked Data 2017-05-15

1. Check in on LDCX action items (https://docs.google.com/document/d/1yr7dIlKzWmaVLf-2easbaQvY5UF8tf0_ylr8RIKWprY/edit):
   1. Get DCE/Tom’s LDF branch of QA merged
      1. The google doc probably misrecorded this as a QA branch; actually a branch on LDF.
      2. There is some prerequisite work, see https://github.com/ActiveTriples/linked-data-fragments/issues/43 – I've asked Tom for an update on that issue.
   2. For LDF gem, Tom would advocate possibly axing rails engine. Wants buy-in for rack instead of rails. First step to test buy-in for this is Tom to create a PR on LDF gem.
      
      1. Seeking more direction on https://github.com/ActiveTriples/linked-data-fragments/issues/8#issuecomment-301089692
   3. Next step for qa-ldf gem, lib/qa/ldf/authority.rb, Tom extracting some of separate concerns that a QA authority deals with - search, mapping between search responses - implement dependency injection to handle those.
      
      1. Anna putting this off for now; will check in again next time.
   4. QA roadmap: Looking at mapping of search responses, open issues that get to a QA either 1.1 or 2.0
      
      1. I think this is a restatement of the item above.
   5. Extending LDF to accept queries: 
      1. Steven did push up the branch on which he started this work: "The branch is located at: https://github.com/ActiveTriples/linked-data-fragments/tree/feature/ldf_query_experimental and has an updated README. I tested it again locally so let me know if there are problems if you try it. Note that it gave me an error in Ruby 2.4 for some reason so I switched back to my older Ruby 2.2.x version."
      2. Anyone who is interested in this functionality is welcome to take a look and pick up this issue!
      3. The LDCX action item is now complete (was simply to get this branch pushed, documented)
2. Summary of Action Items from Linked Data for Libraries bi-annual planning meeting (Lynette Rayle)
   1. Backend
      
      1. Jena-Fuseki as a cache with Lucene/Solr index for searching and potential mirroring
         
      2. Explore ability to submit multiple LDF queries (?s ?p ?o) to search and retrieve predicate values
      3. Integration with ActiveTriples LDF implementation
         
      4. Maintaining QA as usable in Hydra stack but not requiring Hydra stack
   2. Authorities
      
      1. Latest release of QA includes authority access requesting linked data normalized by QA
         
      2. Current QA supports search query and term fetch
      3. Add contextual lookup support in QA linked data configuration
         
      4. QA Current Set of linked data authorities: OCLC Fast, LoC (term fetch only), Agrovoc.  Additionally Geonames is ready in a PR.
      5. Exploring expanding to: VIAF, OrcID, ISNI, dbPedia, LoC (adding search via caching server)
      6. Combining of search results from multiple authorities
   3. Frontend
      
      1. UI for Hyrax that provides contextual lookup
      2. UI for VitroLib (a cataloging tool) that provides contextual lookup
      3. UI considerations when combining multiple authorities in a single result set
   4. Outstanding Questions
      1. How much of the lookup context will happen on the cache server side and how much in QA?
      2. Which has the intelligence for searching the cache, the server or QA?
      3. What search algorithm to use? Some options: purely lexical on primary label (e.g. skos:prefLabel) or on configured text fields (e.g. skos:prefLabel, skos: altLabel, etc.) or support contextual search (providing additional info like birth/death dates in addition to q=person's name)
      4. Cache server returning a predicate with a search ranking as part of the results to allow maintenance of the search order when put into a graph
      5. Do we want to expand cache server search to include resume tokens to allow for larger result sets?
         
3. Do we have membership to sustain this group? If no, what are the next steps?
   1. There's value for us in continuing to touch base.
   2. We'll put out a call for agenda for the next call. If we don't get agenda items we'll do this again next time.
4. Add your project updates / planning topics here!

Next Meeting:  June 19 at 12pst/3est