Page History

...

1. Unit test failures on Linux Mint VMs?
   1. https://vivo-project.slack.com/archives/C8RL9L98A/p1626082946083900
   2. https://vivo-project.slack.com/archives/C8RL9L98A/p1626083526085100
2. Defining shapes or subgraphs for use in APIs, edit forms, indexes etc.
   1. Results of initial experiments with SHACL
   2. Defining more transparent N3-based templates?
   3. Mapping to simplified JSON objects for data ingest
   4. SPARQL for list views/ indexing / URI finding
3. 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 
4. 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
5. 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

References

1. 2019-01 Architectural Fly-in Summary#201901ArchitecturalFlyinSummary-Ingest
2. VIVO in a Box current document for feedback:

   View file
   name VIVOInABoxIdeaProposal210526.pdf height 250

...