Page History

...

1. Dependencies between unit tests
   

   1. Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-2003

       
      1. https://vivo-project.slack.com/archives/C8RL9L98A/p1626082946083900
      2. https://vivo-project.slack.com/archives/C8RL9L98A/p162608352608510
2. VIVO-PROXY
   1. Starting a collaboration with the University of Lausanne for the development of VIVO-PROXY
   2. Forking VIVO-PROXY Repo from UQAM to https://github.com/vivo-community/VIVO-PROXY
3. Defining shapes or subgraphs for use in APIs, edit forms, indexes etc.
   1. Diagrams:
      1. existing architecture: https://docs.google.com/presentation/d/1raO98mklGUQgAc6wMMbgDEsHVk1zoCA3bq4Fyy21GjI/edit?usp=sharing 
   2. Results of initial experiments with SHACL
   3. Defining more transparent N3-based templates?
   4. Mapping to simplified JSON objects for data ingest
      1. Inspiration? William Welling: Apache Marmotta LDPath syntax https://marmotta.apache.org/ldpath/language.html
   5. SPARQL for list views/ indexing / URI finding
4. Moving Scholars closer to the core
   1. Build messaging system first? versus
   2. Original option of typing into existing document modifiers:
      1. "win/win" opportunity: Scholars and VIVO both eliminate some complexity
      2. converting Scholars SPARQL queries to VIVO DocumentModifiers
      3. replacing URIFinders with fast, reliable Solr lookups 
5. Prioritizing future development items:
   1. quick wins / items for a more rapid release
   2. collaborative items for future sprints
   3. (Add/edit at will) spreadsheet: https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing

...