Versions Compared

Old Version 4

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1.  Don Elsborg
  2. Ralph O'Flinn 
  3. Andrew Woods  
    Mike Conlon (star)
  4. Huda KhanSteven McCauley (star)
  5. Jim Blake
  6. Brian Lowe
  7. Benjamin Gross

Agenda

  1. Comments? Architectural fly-in updates

  2. Mailing list messages

    1. jquery.scrollTo error - Do we need to upgrade `jquery_plugins`?
    2. No Subject - "How can I add more associated profiles for that particular  editor."
    3. Freemarker Template Error
    4. [vivo-tech] help regarding the custamization
    5. [vivo-tech] Inferencing engine not adding triples needed
    6. CODE4LIB list: rdf and doi's - thanks Marijane White

  3. Received


    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=14802
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

    1. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1671
       

      1. Benjamin Gross : Pending response to code review

    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1666
       

      1. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design

    3. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1665
       
      1. Should be low-hanging

    4. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1663
       

      1. Where does this stand? What is needed to add more person identifiers to VIVO?

    5. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1644
       
      1. Mike Conlon : thoughts on where this stands?

  4. Status of In-Review tickets

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=14416
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

    1. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1670
       

      1. Kitio Fofack ? Benjamin Gross ? Orcid and i18n

    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1668
       

      1. Only touches one file

    3. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1667
       

      1. Low-hanging - need one more reviewer

    4. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1656
       
      1. Is this feature of broader interest?
    5. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1643
       
      1. Andrew Woods to look into
    6. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1642
       
      1. Mostly trivial, with conversation around Tomcat version support
    7. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1641
       
      1. Relatively straight-forward bug fix
    8. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1661
       
      1. An important step for i18n... resolves many other open issues
    9. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1659
       
      1. Low-hanging, documentation
    10. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1630
       
      1. Kitio Fofack to review?
    11. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1525
       
      1. Low-hanging... need one more review

  5. Bugs (1.11)

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=14702
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


...

Draft notes in Google-Doc

  1. Comments? Architectural fly-in updates

    1. Aligning ingest and interface concerns with the current work

    2. Be helpful to revisit Brian’s diagram at beginning of this fly-in prep meeting

    3. Combine: Stanford’s work into RIALTO

    4. Having indexing/reasoning etc. be separate components that can be configured/set up as desired

      1. Currently indexing is done in a background thread triggered on edit events

        1. Not to say those threads are lower priority

        2. Since on the same processor, may slow things down

        3. 2/3rds of the way there as far as being able to trigger reindexing based on events separately

        4. Bottleneck is still triplestore since index building depends on Sparql queries and does not depend on search index being externalized

          1. Weill Cornell was using Virtuoso but perhaps they are no longer using that

        5. Original push for having a plug and play triplestore so people could try out different back-ends to see what works for them since performance issues

          1. Seems to have been deprioritized with SDB performance improvements

        6. Triplestore replacements will require extensive testing/evaluation

        7. Performance upgrades in one context may yield differing results in other areas

        8. Triplestore canonical data: the current architecture’s assumes this to be the case.  Do we carry that forward?

          1. If not triple-centric, then what does that mean? Practical implications? New code-base?

          2. Linked data at input/output but spectrum of possibilities for internal architecture

          3. Decoupling vs radical departure?

          4. If swapping out triplestores, need testing.  Technical challenge of writing the code is dwarfed by assessing whether this does what we want it to do?

            1. If stepping away from triples, task got a lot bigger

        9. Inclination to tease things apart - be able to integrate smoothly in ecosystem where triplestore is not necessarily canonical data

        10. Inclined to hear about architectures where triplestores not “central”: what is the role of triples in this ecosystem

        11. https://sul-dlss.github.io/rialto/architecture for reference

      2. Inferencing is a blocking call

    5. UI separation

    6. Don is asked for general reflections:

      1. For VIVO core group, incremental changes.  Product evolution group: GraphQL, PostgreSQL etc…

      2. Performance issues not terrible for the profiling system in his experience

      3. Shortcomings of SDB to not handle "optionals" so have to do unions and constructs

      4. Would like to see VIVO do linked open data. So close

      5. With something like Blazegraph and/or performant triplestore, would want to do get all the data (not just public) - should be easy to export data and import it into another triplestore and query like a data warehouse

      6. Since using Symplectic, not invested in features for bringing in external publications, etc. but can see that as useful and perhaps that needs to be a separate module

  2. Mailing list messages

    1. Freemarker template errors: that old nugget

    2. Not all inferencing happening

    3. Messages from agenda:

      1. jquery.scrollTo error - Do we need to upgrade `jquery_plugins`?

      2. No Subject - "How can I add more associated profiles for that particular  editor."

      3. Freemarker Template Error

      4. [vivo-tech] help regarding the custamization

      5. [vivo-tech] Inferencing engine not adding triples needed

      6. CODE4LIB list:rdf and doi's - thanksMarijane White


Actions

  •   

Previous Actions

...