“Unarchive” of repository has happened - per Mike Conlon
Issues for 1.11 -
documentation data distribution running api
Documentation Externalized SOLR?
Andrew: Custom fields documentation? Benjamin
Upgrade tests - 1.9 - Don promises to run upgrade tests (not really)
Any concerns about tests before 1.11 release?
Andrew: Proxy editing? Asked on Slack - no one seems to be familiar with it? No documentation, so hard to test
Florida is using proxy editing
(Benjamin) Data Distributor: artifact id is wrong? 1.10 Or deploy 1.11 artifactId?
Andrew: should be version independent
Andrew: no changes, then keep version
Benjamin: might be confusing, but fine
Mike - update README per pull request? Andrew: Yes
Don: JSON-LD vs Html there are inconsistencies - objects missing - not complete at Colorado at least
List-rdf and JSON-LD as the machine readable formats
Huda: two levels deep, subject->uri-> one more level - just by default - not sure (two level)
Mike: could be problem with custom SPARQL
Don: positions dead-end link - affiliations goes across “relates” - so might be more than two level?
Don will add line-item for that issue (JSON-LD) - under API tests?
Don: LeapFrog trying to use JSON-LD (at Colorado)
Upcoming sprint - week after next (Oct. 14th - Oct. 25th)
Topics listed might need to change
Andrew: consider who can work on sprint
Who can work on what? Topics interested in, availability etc…
Julia - III a) - provide orientation to setting up scholars-discovery, updated scholars-discovery defaults for institutions - data shapes?
Andrew: How many people? Julia: not sure - but is priority to communicat-ize (sp?) of vivo-scholars task force
IV - data shapes, entities? Not sure if that is solidified
Don: baseline that is in scholars-discovery now - shapes - no formal definition - graphql allows you to define the shape that you want (within solr fields options)
But no formal definition
Andrew: idea is (simpler) shapes could inform ingest procedure
Many structures - index document - GraphQL
GraphQL related to data that is coming in - Andrew: should try to mirror ingest procedure by what GraphQL structure (coming out) looks like
Andrew: no clear description of GraphQL data (exactly)
Julia: upfront declaration of entire structure gets in the way of forward progress (of developers) - but they will work on something … ?
Don: planning on ingest Colorado data into - II, III - identify workflow of how to get data into scholars-discovery, test suite - vivo instance is 1.9 though - and then output 1.10, 1.11 to scholars-discovery?
Andrew: updating scholars-discovery turnkey from vivo instance
Don: version problems - particularly with Jena
Don: describe process to import data into scholars-discovery, convert sdb to tdb necessary - 6x better - but 1.9 (old Jena)
Don: try to start a 1.11 instance - and import into scholars-discovery
Andrew: used 1.11 to import openvivo - so it is possible
Mike: SDB might be faster (per upgrades available from Graham)
Mike: Messaging solution to ingest from Vivo? Could be good in this sprint if possible?
Andrew: not sure if William is available in this sprint for that work
Kristina: should be available for sprint - Orchid integration
Ralph? Not here but probably interested in de-coupling TPF - and Nemo Freemarker
Internationalization?
Julia - just met with UQAM (sp?) - may have a developer looking into “content” internalization (Michele)
Julia: would like to line up vivo-scholar with that work
Indicating note-taker