...
Edit capability
Ralph: Changing the editing front-end? Come over to the dark side and join the React effort. (Even used the word synergy. Ralph comes out swinging hard. )
Mike: Editing challenges: (a) russian doll problem (editing object A requires also editing object B and so on). VIVO approaches this by using custom forms for editing (sometimes) and sometimes having the user navigate all the nested relationships. (b) Certain values should be picked from lists so we don’t have 1 million ways of stating a particular department/university. Lookups/controlled vocabularies.
Mike: https://www.project-freya.eu/en/blogs/blogs/the-pid-graph -> working on research graph editing problem. (son of Thor. that’s right, he went there. Oh wait, Thor was a project.)
- Current approach VIVO UI takes:
- Take RDF from a page for a given entity
- Currently, looking at class of objects
- what properties are supported by ontology
- what properties exist
- are any properties controlled
- A "shapes" approach
Karma and The Pump already do a shape->rdf mapping
These tools have already analyzed the nature of the shapes
These tools are still more complex than is currently palatable
Maybe create as a service?
Ingest tools could be smarter (e.g. pulling DOI data)
Shapes provide for expectations in the UI
not all data in the triplestore are not represented in shapes
ability to create custom shapes?
Andrew: Can we align local priorities with the core development priorities?
(We’re all friends)
Ralph: Focusing on core stuff and will move to local later
Andrew: Trying to wrap up sprint work that remains from past sprint. VIVO scholars task force has own sprint underway focusing on read only UI - and this is in line with the work for this sprint. Pattern: extracting data from VIVO into externalized search index and then UI built off that index.
Entities. Where it’s at. Expectations around UI.
Actions
Previous Actions
...